[rabbitmq-discuss] Read all, ack later?

RocknrollArmy rocknrollarmy at googlemail.com
Mon Nov 11 10:52:04 GMT 2013


is it a valid scenario for RabbitMQ to have a queue with persisted 
messages, where a consumer first wants to read all messages from the queue,
but do the ack for all or none of them later on? 

It's about keeping messages in a queue until some consumer criteria decides 
that all messages needed are received. If the criteria fails,
the connection just dies and the messages would remain in the queue until a 
new message arrives and a new consumer connects and does the check again.

Not sure if this is generally a good/bad idea or a use case where a queue 
is the right tool.

Any thoughts on this?

Best regards,


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131111/60111056/attachment.htm>

More information about the rabbitmq-discuss mailing list