<div dir="ltr">Thank you for that information. I will look into federation and then respond to the list if I come across a good answer to my question.<div><br></div><div style>Regards,</div><div style><br></div><div style>
Richard</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 6, 2013 at 12:32 AM, Tim Watson <span dir="ltr"><<a href="mailto:tim@rabbitmq.com" target="_blank">tim@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Richard,<br>
<div class="im"><br>
On 6 Feb 2013, at 06:19, Richard Raseley wrote:<br>
<br>
> Thank you for that information.<br>
><br>
> I am in the process of setting up some test machines now, but based on what I am reading it seems that the bound exchanges must be instantiated within the same RabbitMQ instance or cluster.<br>
><br>
> In my situation I'd like to have a topic exchange that could route to a local queue or "foreign" exchange based on the topic.<br>
<br>
</div>If you want to have interactions between exchanges on separate Rabbit nodes, then you should look at the federation plugin.<br>
<div class="im"><br>
> Would you comment on whether or not that is possible with the "exchange.bind" method?<br>
><br>
<br>
</div>It's not going to be quite that simple, no. But federation may do what you want, with a bit of configuration.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>