[rabbitmq-discuss] Is heartbeat option working in C-client?

[mikel]

Hello,

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
> rabbitmq-c.
>
> -Alan
>
>
> On Sun, Dec 2, 2012 at 2:21 PM, Matthias Radestock <matthias at rabbitmq.com>wrote:
>
>> Alan,
>>
>>
>> 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?
>>
>> Matthias.
>>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130307/d5217754/attachment.htm>