[rabbitmq-discuss] is anybody using 'immediate' publish?

[Randall Richard]

Just curious, are there any benefits for removing it -- is it preventing /
complicating support for other features?

-Randall

On Thu, Sep 13, 2012 at 12:32 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Dear Rabbit users,
>
> AMQP's basic.publish method has two flags - mandatory and immediate - that
> trigger checks at the server and result in messages getting returned to
> clients with basic.return when the necessary conditions aren't met. See
> http://www.rabbitmq.com/amqp-**0-9-1-reference.html#basic.**publish<http://www.rabbitmq.com/amqp-0-9-1-reference.html#basic.publish>for the details.
>
> I can just about see why 'mandatory' may be useful, but 'immediate' has
> always struck me as a bizarre and I fear that anybody using it may well do
> so w/o fully understanding the semantics - can't blame them, it *is*
> bizarre. Because of that, and since it complicates the code in many places,
> we are considering dropping support for 'immediate'.
>
> So is anybody actually using the 'immediate' flag?
>
>
> Regards,
>
> 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/20120914/108ffac2/attachment.htm>