[rabbitmq-discuss] Exchange design to use such that messages sent does not route back?

[stone]

Seems you are looking for a "not" semantics in routing key?
That's probably something AMQP could not provide now. Or?
I would love to see if there is a nice work around though.

/Stone

On Tue, Jun 26, 2012 at 10:05 AM, tang qingxiong <tqxtqx at gmail.com> wrote:

> Some background, currently I am using rabbitMQ as a broker in direct
> mode between applications.
>
> There is X number of applications running at 1 time all binding to the
> same exchange and send out messages with a routing key.
>
> e.g App A will publish message with key "111" and App B, C, D will
> receive the messages A sent. Similarly B, also publish with "111" and
> A ,C,D will receive the message etc.
>
> However I noticed a problem with my design as App A will also receive
> back the message it sent as it consume with the same key. Is there a
> way to configure such that messages sent out does not route back to
> the same application? Thanks
>
> Regards,
> Tang
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120626/e2edb649/attachment.htm>