davidmcote

Thanks Scott! That makes sense. By the way, I found that at least the go client already [has this capability](https://github.com/nats-io/nats.go/blob/main/jetstream/kv.go#L134). I've edited the proposal to include this detail. Our offer...

Related: In https://github.com/nats-io/nats.java/issues/1042, I proposed that the Java NATS client introduce a double-acked `Message.inProgressSync()`, which would benefit further from this proposal.

Thanks Scott! 1/ I am not after exactly-once delivery, which is provably impossible to make reliable, but exactly-once processing. Ie: at-least-once-delivery plus some extra consistency guarantees for acks. (Just wanted...

Thanks for the reply! The proposal of this ticket is a backward compatible change to the KeyValue API which would allow applications to _opt-in_ to using Headers. Existing application code...

Thank you. I appreciate you taking the time to consider this proposal.

FWIW, this scenario is somewhat contrived and not something my application has experienced. I only noticed it through code inspection of NATS clients while contributing an unrelated patch.