<div dir="ltr">Hi, <div>Thanks for the answer.</div><div>As I have mentioned - I need a more than one client to one server. 1 server - n clients. </div><div>my question - I was probably not clear in my mails so I will try to rephrase it one more time. </div>
<div><br></div><div>Can all the clients be configurated with the same queuename ("") and the same routing key (the same for all)? </div><div>That is it.</div><div><br></div><div>thank you .</div><div><br></div><div>
<br><div class="gmail_quote">On Wed, Jul 13, 2011 at 5:53 PM, Michael Bridgen <span dir="ltr"><<a href="mailto:mikeb@rabbitmq.com">mikeb@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"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The RPC servers that serve requests for different applications must be<br>
listening on different work queues. You must ensure that RPC clients use<br>
a routing key that matches the server queue and are different for each<br>
application.<br>
<br>
and also you wrote in the last mail that I Wouldn't need to give each<br>
one a different routing key ( not specifically to support multiple<br>
clients in answer to my second question.<br>
<br>
So, in brief. Should i give the same routing key or shouldnt i?<br>
can each application run with the same routing key and queue and all get<br>
their own answer?<br>
</blockquote>
<br></div>
By far the easiest way to encode RPC is to have one queue per service.<br>
<br>
Many clients may make requests by publishing to that queue. Many clients may answer requests by consuming from that queue.<br>
<br>
If you have disjoint services, use separate queues. To publish to a queue, you use the exchange "" and name the queue in the routing key.<br>
<br>
All the rest follows.<br>
<br>
<br>
--Michael<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Wed, Jul 13, 2011 at 5:23 PM, Emile Joubert <<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a><br></div><div class="im">
<mailto:<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>>> wrote:<br>
<br>
Hi,<br>
<br>
On 13/07/11 14:28, mysurf mail wrote:<br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: *mysurf mail* <<a href="mailto:stammailbox@gmail.com" target="_blank">stammailbox@gmail.com</a><br></div><div class="im">
<mailto:<a href="mailto:stammailbox@gmail.com" target="_blank">stammailbox@gmail.com</a>> <mailto:<a href="mailto:stammailbox@gmail.com" target="_blank">stammailbox@gmail.com</a><br>
<mailto:<a href="mailto:stammailbox@gmail.com" target="_blank">stammailbox@gmail.com</a>><u></u>>><br>
> Date: Wed, Jul 13, 2011 at 4:27 PM<br>
> Subject: Re: [rabbitmq-discuss] a few json rpc questions<br>
> To: Emile Joubert <<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a> <mailto:<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>><br></div><div><div></div>
<div class="h5">
<mailto:<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a> <mailto:<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>>>><br>
><br>
><br>
> Hi Emile,<br>
><br>
> Thanks for the assistance.<br>
><br>
> Though I have read the tutorial in your site, it looks like I did not<br>
> fully understand the rpc for multiple clients' mechanism.<br>
<br>
The RPC classes that you are using are designed to support multiple<br>
clients.<br>
<br>
I would suggest that you get RPC working reliably with a single client<br>
first. The problem you describe (sometimes the application gets stuck)<br>
may not relate to the presence of multiple clients at all.<br>
<br>
The management plugin (<a href="http://www.rabbitmq.com/management.html" target="_blank">http://www.rabbitmq.com/<u></u>management.html</a>) or the<br>
rabbitmqctl utility can be used to confirm queue sizes if you believe<br>
the problem is a messaging one.<br>
<br>
<br>
> I have put a routing key in the server and all the clients (same one)<br>
> and I thought it would make the server handle all the requests.<br>
><br>
> 1. Is there any way to use the rpc like that for multiple clients?<br>
<br>
Yes, as previously stated.<br>
<br>
> 2. Would I need to give each one a different routing key?<br>
<br>
No, not specifically to support multiple clients.<br>
<br>
> 3. Would I need to use different server threads for each client?<br>
<br>
Threading is not a relevant issue here.<br>
<br>
<br>
<br>
<br>
-Emile<br>
<br>
<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</blockquote></div><br></div></div>