[zeromq-dev] zeromq-dev Digest, Vol 46, Issue 5

[Johan Ström]

Hi Pieter!

Good, then I wasn't totally confused! But the theory behind ping  
silence as it was written in the comment is correct, right? As soon as  
a server have sent any kind of reply, we know it's identity has been  
seen, and thus any further pings (to a dead server) will be queued.  
But until we've heard anything, we can ping as much as we want without  
any risk of filled queues.

(Wonder how good this reply goes, only got the digest message..)

Johan

On Oct 3, 2011, at 17:03 , zeromq-dev-request at lists.zeromq.org wrote:
> Hi Johan,
>
> Nice catch on the comments, that section on ping silence is wrong.
> I've fixed it, and am republishing the Guide.
>
> -Pieter
>
> On Mon, Oct 3, 2011 at 5:00 AM, Johan Str?m <johan at stromnet.se> wrote:
>> Hi!
>>
>> I'm studying the FLP model 3 API implementation (http://zguide.zeromq.org/page:all#Model-Three-Complex-and-Nasty 
>>  -> flcliapi: Freelance client API in C).
>> In the comments right after the code, it's mentioned that the  
>> implementation is making use of "ping silence". However, looking at  
>> the actual code I fail to see how that would work?
>>
>> For every loop iteration, ping's are always sent to all the  
>> servers, given that the server's ping_at have been passed. ping_at  
>> is also updated on every ping sent.
>> I've been reading the code up and down, but I fail to see how it  
>> would stop sending pings after server->expires is passed. A server  
>> isn't even "expired" unless there is an active request being  
>> processed.
>>
>> Am I missing something, or are the comments regarding the code wrong?
>>
>> On another note, thank you all for ZeroMQ, it is a really really  
>> lovely library! :)
>>
>> Best Regards
>> Johan
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>>