I was thinking to implement this right away in the library as well.�Considering the comments I'll go that way.<div><br></div><div>Thanks!</div><div><br></div><div>Alvaro<br><div><br><div class="gmail_quote">On Wed, Apr 11, 2012 at 3:39 PM, Michael Bridgen <span dir="ltr"><<a href="mailto:mikeb@rabbitmq.com">mikeb@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 04/11/2012 02:32 PM, Alvaro Videla wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think knowing that every queue is bound to the anon exchange using the<br>
queue name as binding key is not what every user of RabbitMQ knows. It's<br>
more something you learn after you been using RabbitMQ for a while.<br>
<br>
In the case of the exchange I propose the only thing you need to know is<br>
that there exists this other "type of exchange" that lets you do things<br>
"this and that" way. So you declare that exchange and publish to it.<br>
</blockquote>
<br></div>
I don't know why you need a new kind of exchange for this -- isn't it more to do with how the "anonymous exchange" wart is exposed in APIs? For example, node-amqp has a `Connection#publish(queue, msg)`.<br>
<br>
-Michael<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Actually some weeks ago there was a guy on twitter ranting that RabbitMQ<br>
is not reliable:<br>
<a href="https://twitter.com/#!/davekincaid/status/184725072848764928" target="_blank">https://twitter.com/#!/<u></u>davekincaid/status/<u></u>184725072848764928</a> so whether<br>
he's right or not (I replied to him, Alexis did as well) his rant got me<br>
thinking on how to provide something easier for those kinds of users.<br>
<br>
-A<br>
<br>
<br>
On Wed, Apr 11, 2012 at 3:18 PM, Simon MacMullen <<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a><br></div><div class="im">
<mailto:<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>>> wrote:<br>
<br>
� �On 11/04/12 14:13, Alvaro Videla wrote:<br>
<br>
� � � �BTW, I know you can publish messages to the anon exchange by<br>
� � � �using the<br>
� � � �queue name as routing key, but this requires that particular<br>
� � � �knowledge<br>
� � � �of AMQP.<br>
<br>
<br>
� �Sorry, I don't get this argument - won't your hypothetical exchange<br>
� �also require knowledge of AMQP? What is the benefit?<br>
<br>
� �Cheers, Simon<br>
<br>
� �--<br>
� �Simon MacMullen<br>
� �RabbitMQ, VMware<br>
<br>
<br>
<br>
<br></div>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</blockquote></div><br></div></div>