<div dir="ltr">We use shovels for inter-vhost communication like that.<div><br></div><div>Easy and quick. Except you have to restart a cluster member to pick up the config...</div><div><br></div><div>Michael</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sat, Oct 26, 2013 at 4:33 PM, Julian Lyndon-Smith <span dir="ltr"><<a href="mailto:julian+rabbitmq@dotr.com" target="_blank">julian+rabbitmq@dotr.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have a scenario where I need to be able to have a multi-tenant MQ<br>
server, so I started using vHosts.<br>
<br>
However, I also need to be able to route / transfer / forward messages<br>
from a stomp client that is sending to the / vhost to another vhost<br>
based on the queue that the message was sent to<br>
<br>
for example, the stomp client sends to /queue/api/foo.bar , I want to<br>
send the message to vHost foo<br>
<br>
I can , obviously create a stomp client for each tenant, but that<br>
becomes real expensive in resources very quickly and was hoping that<br>
there would be a better way<br>
<br>
Many thanks<br>
<br>
Julian<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>
</blockquote></div><br></div>