[rabbitmq-discuss] Using RabbitMQ Beyond Queueing

Dmitriy Samovskiy dmitriy.samovskiy at cohesiveft.com
Wed Nov 12 15:45:25 GMT 2008

Alexis Richardson wrote:
> On Wed, Nov 12, 2008 at 12:58 PM, Peter Silva <Peter.A.Silva at gmail.com> wrote:

> Apologies - the spec(s) is (are) not always worded to prevent all
> possible misinterpretations.
Thanks Peter for pointing this out, and thanks to Ben and Alexis for detailed overview.

Unlike the spec, a blog post can easily be adjusted and re-worded :)
I rewrote it as follows (additions are marked with underscores).


In no_ack=false mode, a consumer must _eventually_ explicitly acknowledge receipt of each 
message, _individually or as a group (this does not mean that a message must be ack’ed 
before next one can be received)_. If a consumer disconnects without acknowledging, 
_unack’ed_ messages are automatically re-queued for another consumer. This helps achieve 
consumer failover in response to crashes or loss of network connectivity.

I think this sounds clearer now.

- Dmitriy

More information about the rabbitmq-discuss mailing list