[rabbitmq-discuss] Using BlockingConnection in Pika

Jason J. W. Williams jasonjwwilliams at gmail.com
Tue Jul 5 21:52:39 BST 2011

Hi Josh,

I think BlockingConnection has found new life in the latest Pikas. At least
Gavin has put a lot of effort in for those of us that have requested it for
teaching etc.



On Tue, Jul 5, 2011 at 2:50 PM, Joshua Braegger <rckclmbr at gmail.com> wrote:

> Howdy,
> I'm looking at the Pika documentation, and it's mentioning that using
> BlockingConnection is deprecated.  The alternative is to use an
> asynchronous model like SelectConnection.  This works fairly well for
> consumers, but producing one-off messages leaves more to be desired.
> BlockingConnection satisfies the case fairly well -- Create a global
> connection, send many messages, close the connection.  It gets hairy
> when attempting to work asynchronously within a synchronous
> application.  Especially given the fact I want to use the "mandatory"
> flag, and know when any message fails to be enqueued in a synchronous
> manner.
> Are there any best practices to doing this?  Is the answer to just use
> BlockingConnection?
> Thanks,
> -Josh
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> 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/20110705/f5749556/attachment.htm>

More information about the rabbitmq-discuss mailing list