<div>Hi Emile,</div><div> </div><div>I always use topic or direct exchanges. I was confused by that empty string routing key. thanks.</div><div> </div><div>So that means if the exchange is declared topic or direct, that the normal rules will apply. </div>
<div> </div><div>So I suppose the catch-all could be the last fan-out in the alternate exchange chain .</div><div> </div><div>-Steven</div><div> </div><div class="gmail_quote">On 16 February 2012 12:48, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">Hi Steve,<br>
<div class="im"><br>
On 16/02/12 12:13, Steven Taylor wrote:<br>
> so the routing key of "" in the example is a catch-all?<br>
<br>
</div>Sorry I misunderstood your question. The empty routing key has no<br>
special significance in the context of alternative exchanges. Fanout<br>
exchanges ignore the routing key so the it doesn't matter what value you<br>
supply.<br>
<br>
Messages that are sent to the "my-ae" exchange by whatever means<br>
(directly from a publisher or in its capacity as alternative exchange of<br>
"my-direct") will be routed to the "unrouted" queue, regardless of the<br>
message routing keys.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-Emile<br>
</font></span></blockquote></div><br>