Scott Fauerbach

I've talked directly to Neil and Tomasz. There is some clarity to be gained on the explanation of consumer limits, but I don't think there is anything for the client...

Object Store ADR-20 is here https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-20.md

> updating the meta to point to an already existing name should not be allowed It's an error to update an object's name to an existing and not deleted object....

> put should not allow setting the meta.link information - this is only supported via the link API The put method should check the incoming meta for a link and...

@davidmcote This is an architectural issue spanning the server and all clients. I am moving this request to the appropriate repo.

There is no put with revision in KV. There is create which requires no revisions exist for a key. There is update, which requires matching the previous revision. So do...

> Consumers cannot be updated. The only property that’s mutable is the deliver subject. That should probably rule out option 2.

@kozlovic Yes, this is the "subscribe" call does not match the existing consumer. As a team we agreed to gather consensus before implementing client features. The behavior implemented in 803...

My order of preference is 4, 3, 1. 4 would essentially prefer (but not require) that durable consumers should be made ahead of time, before subscriptions, which seems like a...

It was also captured here: https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-6.md which has also been recently updated to reflect the state of the server regarding stream, durable and consumer names.