[rabbitmq-discuss] Using BlockingConnection in Pika
rckclmbr at gmail.com
Tue Jul 5 22:04:53 BST 2011
I bring this up because of this comment --
"*Warning* BlockingConnection is provided for legacy and learning purposes
only and it is not recommended that you use it for a production
The latest git documentation also still has this warning (
"adapters.blocking_connection.BlockingConnection: Enables blocking,
synchronous operation on top of library for simple uses. This is not
recommended and is included for legacy reasons only."
So my question is, why isn't this recommended for production use?
On Tue, Jul 5, 2011 at 2:52 PM, Jason J. W. Williams <
jasonjwwilliams at gmail.com> wrote:
> 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:
>> 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
>> Are there any best practices to doing this? Is the answer to just use
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss