<div class="gmail_quote">On 3 February 2012 14:42, Randall Richard <span dir="ltr"><<a href="mailto:randall@trellisapp.com">randall@trellisapp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>More specifically, for an application that provides a "presence" status, a disconnect is something you want to capture and propagate accordingly. �Is one approach to do what you describe below (e.g. I could create a consumer/service that keeps track of connects and disconnects and associate that with a corresponding application context)? �Is there�something more obvious on how this might be done with RabbitMQ?</div>
</blockquote><div><br>Yes, you could do that (though you might have trouble correlating the
log messages with application-level entities). I don't think there's
anything much cleaner you could do using the built-in features, though.
Stepping away from built-ins, the presence exchange would probably
simplify things in terms of the code you'd need to write, but at the
cost of running a third-party plugin.<br><br>Regards,<br>� Tony<br></div></div>-- <br>Tony Garnock-Jones<br><a href="mailto:tonygarnockjones@gmail.com" target="_blank">tonygarnockjones@gmail.com</a><br><a href="http://homepages.kcbbs.gen.nz/tonyg/" target="_blank">http://homepages.kcbbs.gen.nz/tonyg/</a><br>