Yeah, that does look a bit better than doing a passive declare before every send. I'll give that a shot and see what happens.<br><br>Thanks Matthias!<br>-Alex<br><br><div class="gmail_quote">On Mon, Jun 11, 2012 at 1:06 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alexander,<div class="im"><br>
<br>
On 11/06/12 15:37, Alexander Ward wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
I do this in order to route requests to a specific machine/consumer<br>
cluster by declaring a queue with the name of the machine which is<br>
consuming. I check to see if the queue exists first, and if it does,<br></div>
I route the message to that queue [...], otherwise I send it to a<div class="im"><br>
general queue which is durable.<br>
</div></blockquote>
<br>
You could perhaps employ an alternate exchange<br>
(<a href="http://www.rabbitmq.com/extensions.html#alternate-exchange" target="_blank">http://www.rabbitmq.com/<u></u>extensions.html#alternate-<u></u>exchange</a>) to<br>
accomplish this more elegantly.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br>