I started looking at it and filed a related bug: https://zeromq.jira.com/browse/LIBZMQ-546
Is there documentation for the shutdown sequence? It's fairly complex with the socket, session and two pipes on each end. I currently guess that when a socket is disconnected the peer gets a pipe_term command and that just uses the value of the pipe's 'delay' member (always true) without consulting linger? And what are those delay_on_close/delay_on_disconnect options? Regards, Christian On 07/05/2013 07:45 PM, Pieter Hintjens wrote: > I think they should respect linger, on all transports, since that's what > you'd expect, but it may be hard to implement. > > On Jul 5, 2013 5:27 PM, "Christian Kamm" <k...@incasoftware.de > <mailto:k...@incasoftware.de>> wrote: > > On 07/04/2013 11:47 AM, Ben Gray wrote: > > It appears that disconnect, and unbind, discard all pending messages > > instantly unlike when closing a socket any pending data will wait for > > the linger setting before being discarded. > > > > Is this the expected behaviour, in which case I recommend we > update the > > documentation to mention it, or is this a bug? > > I'd like to second this question, in particular since the behavior seems > to be the opposite for inproc connections - there disconnect lingers > indefinitely regardless of the ZMQ_LINGER variable. > > The desired behavior is that disconnect and unbind respect the linger > setting? > > Cheers, > Christian > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org <mailto:zeromq-dev@lists.zeromq.org> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
