2011/1/25 Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":1al">There is nothing wrong with using exclusive queues for replies. In fact they are nearly always the right choice, which is why our RPC tutorial (<a href="http://www.rabbitmq.com/tutorial-six-python.html" target="_blank">http://www.rabbitmq.com/tutorial-six-python.html</a>) employs them.<br>
<br></div></blockquote><div><br></div><div>I did not mean to say that exclusive queues aren't the right choice for replies.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":1al">
Publish operations do not fail just because a queue doesn't exist</div></blockquote></div><br>Right, because exclusive queue is deleted soon after last consumer disconnects.<div>If responses may take some time in a particular app and client disconnection is probable,</div>
<div>maybe using auto-deleted queues is not such a good idea.<div><div><div>-- <br>MK<br>
</div></div></div></div>