[rabbitmq-discuss] Is heartbeat option working in C-client?
alan.antonuk at gmail.com
Mon Mar 11 21:57:45 GMT 2013
While I cannot comment on what Dawn ended up doing, I can say a few words
about the rabbitmq-c library.
Currently the rabbitmq-c only has partial support for AMQP heartbeats: the
library understands AMQP hearbeats at a protocol level, the library
provides an interface for sending and receiving frames that allows
heartbeat frames to be sent, however the library does not have an event
loop that will automatically handle heartbeats for you.
To use heartbeats with rabbitmq-c you would need to provide your own event
loop/logic to send and receive heartbeat frames.
On Thu, Mar 7, 2013 at 2:09 PM, mikel <triton.genocide at gmail.com> wrote:
> I'm very interested on knowing if Dawn finally resolved that issue related
> with the heartbeat handle from rabbitmq-c driver. I think it's a important
> issue. The hack I'm using is sending an automatic message to the broker
> every x minutes from the rabbitmq-c client, but I would like to solve that
> situation in a correct way.
> Any kind of informatin would be really appreciate.
> On Mon, Dec 3, 2012 at 2:42 PM, Alan Antonuk <alan.antonuk at gmail.com>wrote:
>> Sorry I didn't read Dawn's email all the way through the first time I
>> read it, so Matthais is correct:
>> The library will not do any kind of automatic sending of heartbeats to
>> the broker.
>> 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
>> On Sun, Dec 2, 2012 at 2:21 PM, Matthias Radestock <matthias at rabbitmq.com
>> > wrote:
>>> On 02/12/12 19:04, Alan Antonuk wrote:
>>>> The rabbitmq-c client does not support AMQP heartbeats.
>>> 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.
>>> But if an app sends/receives heartbeats explicitly, as Dawn appears to
>>> be doing, that should work, shouldn't it?
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss