<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/6/6 antony <span dir="ltr"><<a href="mailto:antony.pulicken@gmail.com" target="_blank">antony.pulicken@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":4nv" style="overflow:hidden">Did you mean the temporary queues created/managed by the server ? I<br>
considered it, but then we will end up creating a new queue for each request<br>
in my scenario and that's when I started thinking about a less expensive<br>
option.</div></blockquote></div><br>Named, to be more precise. If you specify queue name as an empty string, RabbitMQ</div><div class="gmail_extra">will generate a unique one and send it back with the queue.declare response.<br>
<br clear="all"><div>If your queues are short lived and only contain a single response, create them as non-durable.</div><div>It's unlikely to introduce a lot of overhead, although it will lead to more network roundtrips but</div>
<div>will reduce the amount of messages your consumers have to requeue because they have different</div><div>correlation ids.</div><div><br></div><div>Which I am guessing will reduce the overall amount of traffic.</div>-- <br>
MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
</div></div>