You could use a direct queue and send the message twice, which<br>is simple but incurs a little extra overhead. There is also potential<br>for the same consumer to process both messages, though I don't<br>know what problem you are really trying to solve so I don't know if<br>
that is ok.<br><br>Is it important that the message is processed twice, or that it be<br>processed by two different consumers?<br><br>- Jim<br><br clear="all">Jim Irrer <a href="mailto:irrer@umich.edu">irrer@umich.edu</a> (734) 647-4409<br>
University of Michigan Hospital Radiation Oncology<br>519 W. William St. Ann Arbor, MI 48103<br>
<br><br><div class="gmail_quote">On Fri, Sep 4, 2009 at 10:17 AM, Benoit Chesneau <span dir="ltr"><<a href="mailto:bchesneau@gmail.com">bchesneau@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all I'm trying to find the best way to process this kind of message :<br>
<br>
I've n consumers waiting on message coming on special routing key. But<br>
I would like that if the message is accepect by 2 of this nodes, all<br>
other ignore it. Any idee how it could be done ?<br>
<br>
For now, I hesitate to just place a dispatcher the publisher and all<br>
consumer nodes that choose where messages should be send. So message<br>
will be pushilesd only to the dispatcher that will republish it to<br>
other nodes.<br>
<br>
Another way to do it may be to make all nodes listening until they<br>
can't. When they can't accept any other actions they will unbind the<br>
queue.<br>
<br>
Is there a better way to do it ?<br>
<br>
- benoit<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="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>