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

[Dan Wise]

Tang,

You could add a header property to the message with App A’s signature (different from other apps) then read this back when the message is received and ignore if found.

Dan.


From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Qingxiong Tang
Sent: 26 June 2012 10:38
To: stone
Cc: "rabbitmq-discuss at lists.rabbitmq.com\""<rabbitmq-discuss at lists.rabbitmq.com>
Subject: Re: [rabbitmq-discuss] Exchange design to use such that messages sent does not route back?

Hi,

  It is what I am looking for as I have only one routing channel and I want everyone to talks in the same channel and except I don't want to hear what I say.

Regards,
Tang

On 26 Jun, 2012, at 5:03 PM, stone <zmstone at gmail.com<mailto:zmstone at gmail.com>> wrote:
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<mailto: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<mailto:rabbitmq-discuss at lists.rabbitmq.com>
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss


________________________________
This email and any attachments are confidential, for the exclusive attention of the recipient and may also be legally privileged or otherwise protected from disclosure. No information contained herein shall be disclosed to any other person without our written consent unless it is clearly publicly available or otherwise specified by us for onward transmission. If you received this email in error, please notify the sender by return email or by telephone on +44 (0)20 7071 0900; do not duplicate or redistribute it by any means; and delete or otherwise destroy all copies whether in electronic or hard copy form.

Any views contained in this email are those of the author and may not reflect those of any Capula entity. We reserve the right to monitor and review all emails within our network to ensure compliance with our policies and to protect our business. Emails are not secure and are not warranted by us to be free of errors nor of viruses nor of other defects which may affect a computer system. Anyone who communicates with us by email is taken to accept these risks. Unless specifically indicated, this email is not an offer or solicitation to buy or sell any investment product. Any information regarding investment products is subject to change without notice.

Capula Investment Management LLP is registered in England no. OC313398 and is authorised and regulated by the Financial Services Authority. Capula Investment Services Ltd is registered in England no. 05460265. The registered office of both companies is 4th Floor Reading Bridge House, George Street, Reading, RG1 8LS. The principal place of business of both companies is 8 Lancelot Place, London SW7 1DR.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120626/090117ed/attachment.htm>