I am trying out ZMQ_STREAM and it's great that (re)-connects are handled asynchronously. However...
Say a TCP server sends out 10000-byte messages such that multiple recv()s are required to get the whole message. A ZMQ_STREAM client receives 1500 bytes and then the connection gets broken. (E.g. server gets killed and restarted) How would the client know to reset its message assembling state if it doesn't know about the disconnection? On Sat, Oct 12, 2013 at 11:49 PM, Pieter Hintjens <[email protected]> wrote: > Indeed... ZMQ_STREAM like all sockets will reconnect opportunistically > so you don't get a formal notification of a closed socket. > > On Fri, Oct 11, 2013 at 9:03 PM, Charles Remes <[email protected]> > wrote: > > Via a timeout. > > > > On Oct 11, 2013, at 12:15 PM, [email protected] wrote: > > > >> How can I detect, that the server has closed a stream client socket ? > >> > >> Marten > >> _______________________________________________ > >> zeromq-dev mailing list > >> [email protected] > >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > > zeromq-dev mailing list > > [email protected] > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
