[rabbitmq-discuss] Newbee consulting question
tomer.paz at gmail.com
Wed Apr 10 11:49:46 BST 2013
that's a good question why not push. Lets just say that it is our system
constraints, its beyond me :)
On Wed, Apr 10, 2013 at 1:44 PM, Ask Solem <ask at rabbitmq.com> wrote:
> On Apr 10, 2013, at 10:06 AM, Emile Joubert <emile at rabbitmq.com> wrote:
> >> we want the architecture to be "pull" rather than "push" in terms of
> >> workers 'asking' the workflow manager to get new tasks when they are
> >> free, rather than task manager pushing tasks to workers blindly.
> > Workers can retrieve messages from a queue synchronously using the
> > basic.get method.
> Why do you think you need to use pull instead of push?
> Are you really sure you want smart dispatch?
> In that case you also have the option of using push, but reroute the
> message to the best worker.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss