<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 16, 2013 at 12:25 PM, Michael Klishin <span dir="ltr"><<a href="mailto:mklishin@gopivotal.com" target="_blank">mklishin@gopivotal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">mezgani ali:<br>
<div class="im"><br>
> No I talk about how to use rabbitmq to distribute task to nodes.<br>
<br>
</div>You can use one queue per worker node and as many consumers as appropriate.<br>
They can communicate back to the main app using HTTP if that's more convenient.<br>
<br></blockquote><div>I think to use only one queue and the nodes will consume what the main app produce like this<br></div><div>the job is distributed and the main app will not worry about how to dispatch tasks to node.<br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Publishing can happen over AMQP 0-9-1 or other protocols RabbitMQ supports via<br>
plugins (STOMP, MQTT, HTTP).<br>
<br>
See [1] to learn more about common messaging scenarios and how to implement<br>
them using RabbitMQ.<br>
<br>
1. <a href="http://www.rabbitmq.com/getstarted.html" target="_blank">http://www.rabbitmq.com/getstarted.html</a><br>
--<br>
MK<br>
<br>
<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>
<br></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Ali MEZGANI<br><b>N</b>etwork <b>E</b>ngineering/<b>S</b>ecurity <br><a href="http://www.nativelabs.org/" target="_blank">http://www.nativelabs.org/</a></div>
</div></div>