Great! That makes a lot more sense now... Cheers,
Brian On Mon, Feb 15, 2010 at 10:49 AM, Martin Sustrik <sust...@250bpm.com> wrote: > Brian, > >>> Anyway, the principle holds. Use ZMQ_UPSTREAM socket to get messages >>> from the previous object, use ZMQ_DOWNSTREAM to send them further on. >> >> I think the docs for ZMQ_UPSTREAM and ZMQ_DOWNSTREAM may have a typo >> that is confusing: >> >> For *both* ZMQ_UPSTREAM and ZMQ_DOWNSTREAM say that >> >> "Send function is not implemented for this socket type." >> >> Doesn't one of these need to have recv? > > This seems to be already fixed in latest docs: > > *ZMQ_UPSTREAM*:: > Socket to receive messages from up the stream. Messages are fair-queued from > among all the connected peers. Send function is not implemented for this > socket > type. > + > Compatible peer sockets: ZMQ_DOWNSTREAM. > > *ZMQ_DOWNSTREAM*:: > Socket to send messages down stream. Messages are load-balanced among all > the > connected peers. Recv function is not implemented for this socket type. > + > Compatible peer sockets: ZMQ_UPSTREAM. > > Martin > -- Brian E. Granger, Ph.D. Assistant Professor of Physics Cal Poly State University, San Luis Obispo bgran...@calpoly.edu elliso...@gmail.com _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
