I think knowing that every queue is bound to the anon exchange using the queue name as binding key is not what every user of RabbitMQ knows. It's more something you learn after you been using RabbitMQ for a while.<div>
<br></div><div>In the case of the exchange I propose the only thing you need to know is that there exists this other "type of exchange" that lets you do things "this and that" way. So you declare that exchange and publish to it.</div>
<div><br></div><div>Actually some weeks ago there was a guy on twitter ranting that RabbitMQ is not reliable:�<a href="https://twitter.com/#!/davekincaid/status/184725072848764928">https://twitter.com/#!/davekincaid/status/184725072848764928</a>�so whether he's right or not (I replied to him, Alexis did as well) his rant got me thinking on how to provide something easier for those kinds of users.</div>
<div><br></div><div>-A</div><div><br><br><div class="gmail_quote">On Wed, Apr 11, 2012 at 3:18 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 11/04/12 14:13, Alvaro Videla wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
BTW, I know you can publish messages to the anon exchange by using the<br>
queue name as routing key, but this requires that particular knowledge<br>
of AMQP.<br>
</blockquote>
<br></div>
Sorry, I don't get this argument - won't your hypothetical exchange also require knowledge of AMQP? What is the benefit?<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br></div>