Sorry I didn't read Dawn's email all the way through the first time I read it, so Matthais is correct:<div><br></div><div>The library will not do any kind of automatic sending of heartbeats to the broker.</div><div>
<br></div><div>The library should be able to be used in such a way that you could correctly implement heartbeats, though I have not seen it been done with rabbitmq-c.</div><div><br></div><div>-Alan<br><br><div class="gmail_quote">
On Sun, Dec 2, 2012 at 2:21 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Alan,<div class="im"><br>
<br>
On 02/12/12 19:04, Alan Antonuk wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The rabbitmq-c client does not support AMQP heartbeats.<br>
</blockquote>
<br></div>
In the sense that it is not automatically sending heartbeats in the absence of other traffic, and is not automatically monitoring inbound traffic/heartbeats? Sure.<br>
<br>
But if an app sends/receives heartbeats explicitly, as Dawn appears to be doing, that should work, shouldn't it?<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br></div>