[rabbitmq-discuss] accept a message on a limited number of consumer

Jim Irrer irrer at umich.edu
Fri Sep 4 16:15:47 BST 2009

The only other thing I can think of is to have two types of consumers, 'A'
and 'B,
with corresponding exchanges, and send messages out once to each of the
exchanges.  This is a suboptimal because you lose any global load balancing
or fault tolerance.  It could also be done with header values.

That's all I've got.

I am curious as to why 2 consumers.  Is it that the processing needs to be
verified, is there a trust issue, or something else?  If the reason is
applicable, then maybe a feature should be added to AMQP to support it.

- Jim

On Fri, Sep 4, 2009 at 10:47 AM, Benoit Chesneau <bchesneau at gmail.com>wrote:

> On Fri, Sep 4, 2009 at 4:38 PM, Jim Irrer<irrer at umich.edu> wrote:
> > You could use a direct queue and send the message twice, which
> > is simple but incurs a little extra overhead.
> The problem here is that I could have a lot of nodes behind. But this
> solution seem simple.
> > Is it important that the message is processed twice, or that it be
> > processed by two different consumers?
> It's important that the message is processed/accepted by 2 nodes. Each
> nodes will be in its own machine  hand have a limited number of
> specific message it can treat.
> - benoit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090904/d25287f1/attachment.htm 

More information about the rabbitmq-discuss mailing list