<div dir="ltr">Hi Michael,<div><br></div><div>It's a little more than presence. It is not enough to know the service is running-- I need to know if it can handle a message right now. So I guess I would need to use a solution to keep track not only of presence but of capacity-- which might be hard to do in a transactional manner.</div>
<div><br></div><div>Still-- your point is taken and may be the best solution given the requirements and capabilities.</div><div><br></div><div>Thanks,</div><div>Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Oct 21, 2013 at 4:24 PM, 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 21 Oct 2013, at 23:52, Chris <<a href="mailto:stuff@moesel.net">stuff@moesel.net</a>> wrote:<br>
<br>
> Question #1: Is there some other way of doing it that I'm not thinking of?<br>
<br>
</div>This is basically a presence problem. I'd recommend using a coordination<br>
service such as etcd or ZooKeeper, or at least a K/V store like Redis, when<br>
you need presence or coordination between publishers and consumers.<br>
<br>
MK<br>
<br>
<br>
<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>