<div dir="ltr">Hi Simon,<div><br></div><div>Ah! �I didn't notice that bit about upstream sets, but now that you mention it, I can see what you mean... �I'll look into that. �I'm a little concerned about my other approach since it would create more traffic than necessary. �In the end, maybe I will just need to make a way for consumers to dynamically determine their broker's dedicated exchange names. �But first I'll look further into the upstream sets!</div>
<div><br></div><div>Thanks,</div><div>Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 8, 2013 at 4:41 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">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 07/10/2013 21:53, Chris wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I essentially want to federate an exchange such that the "upstream"<br>
exchange name is different than the exchange name that the downstream<br>
queues bind to.<br>
</blockquote>
<br></div>
You can set an "exchange" property on an upstream or an upstream set, which will override the name of the upstream exchange to connect to. It'll likely mean you need to define one upstream per downstream exchange.<br>
<br>
I see this is not explained terribly well in the documentation. Will fix.<br>
<br>
<snip alternate approach><div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is this how you would recommend it?<br>
</blockquote>
<br></div>
If I understand your use case, the approach above would be simpler.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Does this defeat RabbitMQ's smart routing?<br>
</blockquote>
<br></div>
Yes it would. Federation only takes account of routing decisions made in the federated exchange, not any exchanges using it as a source through e2e bindings.<br>
<br>
Cheers, Simon<br>
<br>
</blockquote></div><br></div>