matt_weinstein at yahoo.com
Wed Aug 11 18:57:22 CEST 2010
I've pushed a new version of zmq_reactor which fixes the
zmq_reactor_pair problems, and has test code.
I've also rearranged the samples subdirectory, and there is now a
This has built and tested on a Mac, I'll move to Linux soon .... ;-)
This should fix the concerns with zmq_pair. When creating a pair, I
now allocate a "one-time" struct that passes the appropriate data to
the connecting thread.
This requirement will go away once sockets can be ported between
threads (but I will probably leave the interface the same since it can
implement the socket-moving code as required).
Please feel free to send questions -- documents are overdue for this.
On Aug 11, 2010, at 9:45 AM, Ilja Golshtein wrote:
> few not very systematical questions about zmq_reactor.
> In zmq_reactor_pair ZMR_REQ and ZMQ_PAIR are connected. Is it a
> typo, or such a combination really possible? How does it work?
> The implementation of ZMQ_REACTOR_OPS_* is more or less clear,
> though could you provide some example usage. What is this technique
> useful for? When is it necessary to shift _start_ in order to
> exclude some reactors from poll?
> Don't you afraid these goto-like things lead to ununderstandible code?
> If these questions are answered in the List or in a general source
> of information - I would be happy with a link.
> 10.08.10, 21:35, "Matt Weinstein" <matt_weinstein at yahoo.com>:
>> (The zmq_reactor library should help a bit here, that's what I'm
>> for all this...)
> Best regards,
> Ilja Golshtein.
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
More information about the zeromq-dev