Scott Fauerbach

As an example, the Java / .net client allow the user to skip the subject when they indicate bind.

The java /.net clients perform filter validation and check for consumer changes even when the user specifies to bind.

I've marked my additions to pull requests as EXPERIMENTAL so we can change them without a break if we need to.

The new max_bytes on a pull (JSApiConsumerGetNextRequest) Let's say you set max_bytes to 1k, but have a message that is 2k. What will happen?

It would be nice if we didn't have to rely on text for status messages. We face the same issue with flow control and heartbeats, we have to recognize the...

Maybe this can be a store specific option. I could see in the future that there will be other store specific options, we might as well think about ways to...

@derek said this in slack: > By default the delete should be like limits, secure erasing should be opt in imo. Been there since launch of JetStream I believe for...

How would people feel about this: In JetStream Management, change DeleteMessage to set no_erase to true and add SecureDeleteMessage which sets no_erase to false or leaves it empty ? +/-

Another option would be to leave DeleteMessage as is, and add InsecureDeleteMessage

Please confirm your client already supports this or add it to your to-do.