Byron Ruth

Thanks @a-h. I will be reviewing this in the next day or two. It prompted me to dig into the concrete permissions required depending on the consumer and stream requirements.

@delaneyj In the context of JetStream, https://github.com/nats-io/nats-server/issues/2515 would be applicable. For core pub/sub, I suppose a declaration of `us.zip.{89129,90210,12345}.*` would have the server manage the pattern matching and distribution over...

The [zepto](https://github.com/bruth/synapse/blob/master/src/synapse/zepto.coffee) backend may be worth looking at too.

Can you describe what you mean by "declarative wrapper"?

Is this still relevant? Or is there more context?

My takeaway of this is that It boils down to a client holding an exclusive lock for delivery of messages while connected. Once disconnected/timed out, there is a switch. The...

Use case aside, the one concern I have is that `LoadLastMsg` is not nearly as optimized with a pattern as it is with a concrete subject. This is already known...

Good observation. Since dateutil (`duparse`) will try to infer what it can, so there are likely a bunch of other edge cases that could be hit. This may need to...

@fmeyer Have anymore thoughts on this?

@ripienaar For the schema and CLI, it appears you checked these off, but the PRs apply to the metadata fields rather than support for multiple subject filters.