Thanks Pieter, I've made a couple of tries in the meantime and it seemed like its sufficient to read ZMQ_EVENTS after the final part of the multipart message. But maybe I was just lucky so far and one really needs to do it every time..
Tobias Am 14.02.2013 04:35, schrieb Pieter Hintjens: > On Mon, Feb 11, 2013 at 2:45 PM, Tobias Scharnberg > <[email protected]> wrote: > >> The returned file descriptor is also used internally by the zmq_send and >> zmq_recv functions. As the descriptor is edge triggered, applications >> must update the state of ZMQ_EVENTS after each invocation of zmq_send or >> zmq_recv. > This is a dramatically poor explanation that has tripped up many people. > > I've not used this option but from reading the code, this is what it > means: reading the ZMQ_EVENTS socket option has the side-effect of > processing commands internally. So you will have to (afaiu) read that > option after sending/receiving each part. > > -Pieter > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev -- Tobias Scharnberg Software Public Address Systems Tel. +49 4101 69699-20 :: Fax +49 4101 69699-18 [email protected] WENZEL Elektronik GmbH :: Gehrstücken 7 :: 25421 Pinneberg, Germany www.wenzel-elektronik.de Sitz und Registergericht: Pinneberg, HRB 9316 PI USt-IdNr.: DE 812946778 Geschäftsführung: Dipl.Ing. Jörg Simon, Dr. Volker Henkel _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
