<font face="arial" size="2"><p style="margin:0;padding:0;">Thanks for the help Alexis but the scenario is a little more complicated... I think exchange binding is the only way to go... but I'm open for suggestions ;)</p>
<p style="margin:0;padding:0;">&nbsp;</p>
<p style="margin:0;padding:0;">Users are able to log-on to the system using more than one device at the same time (mobile, web, desktop) and it is a requirement that messages are delivered to each of these devices even if they are all logged on at the same time. Sooo... I am looking at exchange binding like:</p>
<p style="margin:0;padding:0;"><span style="font-size: 10pt;"> </span></p>
<p style="margin:0;padding:0;">&nbsp;</p>
<p style="margin:0;padding:0;">P -&gt; Topic Exchange &lt;------------<span style="font-size: 10pt;">User1Exchange</span><span style="font-size: 10pt;"> </span></p>
<p style="margin:0;padding:0;">|_________temporary Q mobile</p>
<p style="margin:0;padding:0;">|________temporary Q web</p>
<p style="margin:0;padding:0;"><span style="font-size: 10pt;">|_________temporary Q desktop </span></p>
<p style="margin:0;padding:0;">&nbsp;</p>
<p style="margin:0;padding:0;">&nbsp;</p>
<p style="margin:0;padding:0;"><span style="font-size: 10pt;">Functional Requirements:</span></p>
<p style="margin:0;padding:0;"><span style="font-size: 10pt;">Topic exchanges </span></p>
<p style="margin:0;padding:0;"><span style="font-size: 10pt;">Messages published to exchange while user offline are available when user logs-on</span></p>
<p style="margin:0;padding:0;"><span style="font-size: 10pt;">One "permanent address" per user (thought of queue - looks like I need exchange)</span></p>
<p style="margin:0;padding:0;"><span style="font-size: 10pt;">multiple instances of the same user logged-on concurrently</span></p>
<p style="margin:0;padding:0;">&nbsp;</p>
<p style="margin:0;padding:0;"><span style="font-size: 10pt;"><br /></span></p>
<p style="margin:0;padding:0;">&nbsp;</p>
<p style="margin:0;padding:0;">-----Original Message-----<br />From: "Alexis Richardson" &lt;alexis@rabbitmq.com&gt;<br />Sent: Monday, April 16, 2012 6:33pm<br />To: m.luchak@smartasking.com<br />Cc: rabbitmq-discuss@lists.rabbitmq.com<br />Subject: Re: [rabbitmq-discuss] exchange.bind details<br /><br /></p>
<div id="SafeStyles1334621226">
<p style="margin:0;padding:0;">Matthew<br /><br />Have you tried using direct exchanges?<br />http://www.rabbitmq.com/tutorials/tutorial-three-python.html<br /><br />alexis<br /><br /><br />On Mon, Apr 16, 2012 at 11:24 PM,  &lt;m.luchak@smartasking.com&gt; wrote:<br />&gt; Hi all,<br />&gt;<br />&gt;<br />&gt;<br />&gt; Thanks for the help with the STOMP question. I am having difficulties<br />&gt; understanding the exchange.bind constructor (ticket, destination,<br />&gt; source).... Could someone please point me to resources?<br />&gt;<br />&gt;<br />&gt;<br />&gt; I am trying to implement "exchange.bind"<br />&gt; &nbsp;(http://www.rabbitmq.com/blog/2010/10/19/exchange-to-exchange-bindings/) to<br />&gt; allow multiple instances of the same user presence (android, web, desktop)<br />&gt; to receive notifications.<br />&gt;<br />&gt;<br />&gt;<br />&gt; Under the exchange-&gt;Q model if all three devices are logged in concurrently<br />&gt; there is no way for all instances to receive messages as they will all be<br />&gt; logged in on the same Q.<br />&gt;<br />&gt;<br />&gt;<br />&gt; thanks,<br />&gt;<br />&gt; Matthew<br />&gt;<br />&gt;<br />&gt;<br />&gt;<br />&gt;<br />&gt;<br />&gt; _______________________________________________<br />&gt; rabbitmq-discuss mailing list<br />&gt; rabbitmq-discuss@lists.rabbitmq.com<br />&gt; https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss<br />&gt;</p>
</div></font>