[zeromq-dev] Dealer send succeeded/failed
Pieter Hintjens
ph at imatix.com
Tue Jun 4 17:11:16 CEST 2013
Erwin,
Sorry for the late reply, I'm at a conference. You will find numerous
examples that do what you need in Chapter 4 of the Guide. Heartbeating
is part of it, but there are other aspects too, such as failover and
retries. To properly build this you should work through the examples
until you understand each type of failure that can affect your
use-case, and how to detect it and deal with it.
-Pieter
On Tue, Jun 4, 2013 at 4:21 PM, Erwin Karbasi <erwin at optinity.com> wrote:
> Hi Martin,
>
> Thank you a lot for clear explanation.
> We need to implement heartbeating feature.
>
> Cheers,
> Erwin
>
> On Jun 4, 2013 3:33 PM, "Martin Sustrik" <sustrik at 250bpm.com> wrote:
>>
>> Hi Erwin,
>>
>> No it is not possible to detect the failure of the peer. The problem is
>> inherently semi-decidable, i.e. you can make sure that peer is alive (if it
>> responds), but there's no way to distinguish a peer failure from a slow/dead
>> network.
>>
>> Thus the only thing you can do is a handshake with the peer and if
>> response isn't received in, say, 1 minute, consider the peer dead. Of
>> course, you won't be 100% sure -- it can still be caused by network failure,
>> congestion or somesuch.
>>
>> Martin
>>
>> On 04/06/13 13:54, Erwin wrote:
>>>
>>> Hi Guys,
>>>
>>> Any help please.
>>>
>>> Thanks,
>>> Erwin
>>>
>>> _______________________________________________
>>> zeromq-dev mailing list
>>> zeromq-dev at lists.zeromq.org
>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
More information about the zeromq-dev
mailing list