Let me show one more example.�<div><br></div><div>I've got some moderation queue. Whenever a moderator locks message (or several messages) for moderation, it moves from main queue to personal moderator's queue. Just to perform some long time lock (It can be minute or hour, thus I can't use ack/nack to hold message in main queue). The goal is to monitor all moderators queues as well as main one. The problem is that I do not know all moderator's queues and I can't just monitor some fixed list because it regenerates dynamically.�</div>
<div><br></div><div>I've just thought about using separate exchange for moderator's queues. It can help with monitoring, I'd watch over whole exchange.�</div><div>But it is still interesting�whether I can publish message to several queues and consume it from them all at once. Sounds like gibberish.�</div>
<div><br></div><div>To be honest I've got one more problem to solve - it is to automatically release these locks (put a message from moderator's queue back to main) by timeout, but it should be other conversation I think :)�</div>
<div><br></div><div>Best regards, Ostin.</div><div><br><div class="gmail_quote">20 ������ 2012��. 21:00 ������������ Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span> �������:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 20/04/12 17:27, ostin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Example application with topic exchange:<br>
I push a message to server1.app1 queue and an other one to<br>
server1.app2 queue. I monitor server1 queue to determine count of<br>
processing messages on server 1. After app1 ends processing message it<br>
shold be deleted from both queues: from app1 to prevent duplicate<br>
processing, from server1 to have valid stats for monitoring. I assume<br>
that there can be many applications with random names, so I cant<br>
monitor just count of messages in app* queues.<br>
</blockquote>
<br>
If you want to make sure that a given message is only ever consumed from server1.app1 OR server1.app2, why not have only a single queue and have both applications consume from it?<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br></div>