[rabbitmq-discuss] Federated Exchange Upstream / Downstream Names

[Chris]

Hi Simon,

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!

Thanks,
Chris


On Tue, Oct 8, 2013 at 4:41 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 07/10/2013 21:53, Chris wrote:
>
>> I essentially want to federate an exchange such that the "upstream"
>> exchange name is different than the exchange name that the downstream
>> queues bind to.
>>
>
> 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.
>
> I see this is not explained terribly well in the documentation. Will fix.
>
> <snip alternate approach>
>
>
>  Is this how you would recommend it?
>>
>
> If I understand your use case, the approach above would be simpler.
>
>
>  Does this defeat RabbitMQ's smart routing?
>>
>
> 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.
>
> Cheers, Simon
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131008/bcdabd89/attachment.htm>