Here are examples of this logic for the req/rep sockets: http://github.com/zeromq/zeromq2/blob/v2.0.8/src/rep.cpp#L176 http://github.com/zeromq/zeromq2/blob/v2.0.8/src/rep.cpp#L176
I just went over this logic with Sustrik a few days ago because we had to understand it in the Python bindings. Cheers, Brian On Wed, Sep 22, 2010 at 3:24 PM, Brian Granger <[email protected]> wrote: > On Wed, Sep 22, 2010 at 2:47 PM, Pieter Hintjens <[email protected]> wrote: >> On Wed, Sep 22, 2010 at 2:08 PM, Pieter Hintjens <[email protected]> wrote: >> >>> Strange. I remember discussing this with Martin Sustrik and hearing, >>> "when a message is sent 0MQ nullifies it". >> >> OK, so the user guide is wrong on this. Sending a message is safe and >> does not affect it. Receiving _into_ an existing message will nullify >> the message first. >> >> Wires got crossed somewhere... sorry about that. >> >> You can send the same message N times safely. > > No, I don't think this is correct. Hold on a second... > > Brian > >> - >> Pieter Hintjens >> iMatix - www.imatix.com >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > > > > -- > Brian E. Granger, Ph.D. > Assistant Professor of Physics > Cal Poly State University, San Luis Obispo > [email protected] > [email protected] > -- Brian E. Granger, Ph.D. Assistant Professor of Physics Cal Poly State University, San Luis Obispo [email protected] [email protected] _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
