Hi Josh,<div><br></div><div>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.</div><div><br></div><div><a href="https://github.com/rabbitinaction/sourcecode/blob/master/python/chapter-2/hello_world_producer.py">https://github.com/rabbitinaction/sourcecode/blob/master/python/chapter-2/hello_world_producer.py</a></div>
<div><br></div><div>-J<br><br><div class="gmail_quote">On Tue, Jul 5, 2011 at 2:50 PM, Joshua Braegger <span dir="ltr"><<a href="mailto:rckclmbr@gmail.com">rckclmbr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">Howdy,<br><br>I'm looking at the Pika documentation, and it's mentioning that using<br>
BlockingConnection is deprecated. The alternative is to use an<br>asynchronous model like SelectConnection. This works fairly well for<br>consumers, but producing one-off messages leaves more to be desired.<br>BlockingConnection satisfies the case fairly well -- Create a global<br>
connection, send many messages, close the connection. It gets hairy<br>when attempting to work asynchronously within a synchronous<br>application. Especially given the fact I want to use the "mandatory"<br>flag, and know when any message fails to be enqueued in a synchronous<br>
manner.<br><br>Are there any best practices to doing this? Is the answer to just use<br>BlockingConnection?<br><br>Thanks,<br><font color="#888888">-Josh</font></span>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>