<div dir="ltr">that's a good question why not push. Lets just say that it is our system constraints, its beyond me :)</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 10, 2013 at 1:44 PM, Ask Solem <span dir="ltr"><<a href="mailto:ask@rabbitmq.com" target="_blank">ask@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"><br>
On Apr 10, <a href="tel:2013" value="+9722013">2013</a>, at 10:06 AM, Emile Joubert <<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>> wrote:<br>
<br>
>> we want the architecture to be "pull" rather than "push" in terms of<br>
>> workers 'asking' the workflow manager to get new tasks when they are<br>
>> free, rather than task manager pushing tasks to workers blindly.<br>
><br>
> Workers can retrieve messages from a queue synchronously using the<br>
> basic.get method.<br>
<br>
<br>
</div>Why do you think you need to use pull instead of push?<br>
Are you really sure you want smart dispatch?<br>
<br>
In that case you also have the option of using push, but reroute the<br>
message to the best worker.<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><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><br></div>Rgrds<br>Tomer</div>
</div>