[rabbitmq-discuss] .NET API - Using PublishConfirms to get Reliability

Matthias Radestock matthias at rabbitmq.com
Wed Feb 26 07:40:31 GMT 2014

On 26/02/14 07:15, Michael Klishin wrote:
> This is not how publisher confirms are mean to be used in the client.
> It’s fine to manually acquire next delivery tag and use it. However,
> you should consider using IModel#WaitForConfirms which will wait
> until all outstanding acks arrive or a timeout is reached.

What the OP is doing is actually fine. Unlike WaitForConfirms, it 
potentially allows for completely async, streamed processing of confirms 
without ever waiting.

However, the OP didn't post the code for processing the confirms, so 
there may well be bugs hiding in that.


More information about the rabbitmq-discuss mailing list