Aleksandr Antonov

[Related issue](https://github.com/nats-io/nats-server/issues/4891).

> Personally for this kind of use case I use a combination of KV and WorkQueue. > > KV stores the task state and data while work queue is there...

> AckInProgress is about as heavy as a heartbeat tbh :) A single ack is enough and thats the default supported behavior. You only need to send in progress when...

> Yes, so how is the consumer supposed to know your worker is still there? You have to tell it. That's ack in progress. Its necessary but also optimized for...

> it's okay to have a consumer, getting messages in batch mode, and send single InProgress for entire batch and have option to nack some messages due to anti-affinity functionality.

> No we dont have batch acks. You have to send them one by one I am afraid. > > You could look to something like a unacknowledged consumer (see...

> Do you have multiple clients reading a consumer? Or just one client:one consumer? The All ack strategy only really work with 1:1 client:consumer. > > Agree though we do...

> Then none of the All acks will work for you. Kinda sad, but Issue is all about support this type of communication for NATS.

> When I say it doesnt work I mean the entire concept does not work, its not like oh just add one feature. It's about the basics of the physical...

> So this is not about sending to other subjects, which we can lock down, but for valid subjects just to rate limit yes? Yes. Even for allowed subjects, if...