[rabbitmq-discuss] Reliable "publishing"

[Simone Busoli]

Guarantees under which circumstances specifically? I'm thinking about
connection shutdowns, broker crashes, this kind of events. Let me clarify
that I'm just trying to understand, as I'm building a library which
encapsulates this behavior using publisher confirms, and I'm facing the
problem of making sure that all messages reach the destination, and thus
what to do when messages are not (n)acked by the broker, if that can ever
happen.

On Tue, Dec 20, 2011 at 17:31, Matthias Radestock <matthias at rabbitmq.com>wrote:

> On 20/12/11 16:19, Busoli, Simone wrote:
>
>> Therefore I'm wondering whether a mechanism, perhaps an options of
>> the shovel and federation plugins (every x messages, every x seconds,
>> ...), to process messages which have remain unconfirmed for some time
>> should be introduced.
>>
>
> The server guarantees that every message requiring confirmation is
> eventually either ack'ed or nack'ed. So I don't see what a timeout would
> accomplish.
>
> Matthias.
>
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20111221/ebf4c2b4/attachment.htm>