[zeromq-dev] Controlling initial connection retry/timeout
Pieter Hintjens
ph at imatix.com
Sat Apr 11 13:48:36 CEST 2015
People do this, though IMO it's not a great idea. Monitor events are
asynchronous and by definition out of date. Also you often want to
keep client connections alive if TCP connections go down and come back
up.
On Thu, Apr 9, 2015 at 12:21 PM, Benson Margulies <benson at dchbk.us> wrote:
> A small supplementary question,
>
> is it typical for production apps to use socket monitors to keep track
> of the existence of connections to peers?
>
>
> On Thu, Apr 9, 2015 at 1:22 AM, Andrew Hume <andrew at humeweb.com> wrote:
>> i wasn’t trying to cause trouble, and thanks for the clarification.
>>
>>> On Apr 8, 2015, at 10:20 PM, Pieter Hintjens <ph at imatix.com> wrote:
>>>
>>> OK, my answer was probably wrong, though IMO it was consistently wrong
>>> :-) I did say "reconnect" is after any successful connect.
>>>
>>> A closer reading indicates this applies to all attempts to connect
>>> including the first one, and "reconnect" means an attempt to connect
>>> rather than recovery after a broken connection.
>>>
>>> The man page and option names could be better worded.
>>>
>>> -Pieter
>>>
>>> On Thu, Apr 9, 2015 at 7:12 AM, Andrew Hume <andrew at humeweb.com> wrote:
>>>> with all due respect, this answer seems self-contradictory.
>>>> the first connection is not a reconnect, so it is special in that sense.
>>>> but i take from your answer ZMQ_RECONNECT_IVL does not apply to the first connection.
>>>> is that correct?
>>>>
>>>>> On Apr 8, 2015, at 10:02 PM, Pieter Hintjens <ph at imatix.com> wrote:
>>>>>
>>>>> "reconnect" means after any successful connection. The first
>>>>> connection has no special semantics.
>>>>>
>>>>> On Wed, Apr 8, 2015 at 10:25 PM, Benson Margulies <bimargulies at gmail.com> wrote:
>>>>>> Does
>>>>>>
>>>>>> ZMQ_RECONNECT_IVL
>>>>>>
>>>>>> apply to the first connection made for a socket for a peer, or only
>>>>>> reconnections after a first connection was successful. Is there any
>>>>>> control on how ZMQ treats problems establishing an initial connection?
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>> _______________________________________________
>>>> 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
>>
>> _______________________________________________
>> 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