Seems you are looking for a "not" semantics in routing key?<div>That's probably something AMQP could not provide now. Or?</div><div>I would love to see if there is a nice work around though.</div><div><br></div>
<div>/Stone<br><br><div class="gmail_quote">On Tue, Jun 26, 2012 at 10:05 AM, tang qingxiong <span dir="ltr"><<a href="mailto:tqxtqx@gmail.com" target="_blank">tqxtqx@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Some background, currently I am using rabbitMQ as a broker in direct<br>
mode between applications.<br>
<br>
There is X number of applications running at 1 time all binding to the<br>
same exchange and send out messages with a routing key.<br>
<br>
e.g App A will publish message with key "111" and App B, C, D will<br>
receive the messages A sent. Similarly B, also publish with "111" and<br>
A ,C,D will receive the message etc.<br>
<br>
However I noticed a problem with my design as App A will also receive<br>
back the message it sent as it consume with the same key. Is there a<br>
way to configure such that messages sent out does not route back to<br>
the same application? Thanks<br>
<br>
Regards,<br>
Tang<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br></div>