<div dir="ltr">OK - thanks for the prompt response Michel.<br><br>While the trigger monitor part looks easy, it will need to relly on the exchange to generate the trigger msg using parameters tied to the apps msg queue. That way the one trigger queue can be used by numerous queues to trigger different apps. However with the way messages can be duplicated in RabbitMQ it might be possible to use a second copy of the data in a second queue to trigger the app.... food for thought. i better start coding a trigger monitor daemon!<br>
<br><br>Sid<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 7, 2013 at 3:24 AM, Michael Klishin <span dir="ltr"><<a href="mailto:mklishin@gopivotal.com" target="_blank">mklishin@gopivotal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 6 Nov 2013, at 15:42, Sid Young <<a href="mailto:sid.young@gmail.com">sid.young@gmail.com</a>> wrote:<br>
<br>
> Does this functionality exist in RabbitMQ in any form???<br>
<br>
</div>Nothing like that is built in but a pretty trivial message consumer app can do that<br>
(and will give you a lot of flexibility).<br>
<br>
MK<br>
<br>
Software Engineer, Pivotal/RabbitMQ<br>
<br>
<br>
</blockquote></div><br><br clear="all"><br>
</div></div>