[zeromq-dev] missing events ZMQ_FD / ZMQ_EVENTS

Gerhard Lipp gelipp at googlemail.com
Wed May 2 11:45:59 CEST 2012

On Wed, May 2, 2012 at 11:27 AM, Paul Colomiets <paul at colomiets.name> wrote:
> Hi Gerhard,
> On Wed, May 2, 2012 at 10:11 AM, Gerhard Lipp <gelipp at googlemail.com> wrote:
>> hello paul!
>> i dont understand the background of your approach. why should the src
>> fd's io handler check the dst's events (and vice versa)?
> It's the simplest way I've found to solve a problem.
>> even if this worked in this scenario, wouldn't it be a coincidence?
> No, it's not coincidence.
>> well, at least it is better than busy waiting / polling ...
> Yes. There are various way to optimize presented code, I've
> just picked up something on to of my head.

I really appreciate any help and ideas to solve this issue! I just did
not get the idea behind this attempt.
Could you explain it in more detail (something particular to observe)?

> On Wed, May 2, 2012 at 11:26 AM, Gerhard Lipp <gelipp at googlemail.com> wrote:
>> btw, using the build in poller just works:
> Yes the builtin poller works in intuitive way.
> ZMQ_FD is meant for experts. So if you don't
> understand how it works, you can just use
> builtin poller without the problems.

I need to use the ZMQ_FD together with libev to get my other IO
handled in the same process.
The doc is pretty clear about using it (together with ZMQ_EVENTS) and
I just don't understand why the x.lua is blocking when handling x.req
> 1 instances. The egde-triggered fashion of handling the fd is
treated just right in my opinion.

> --
> Paul
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

More information about the zeromq-dev mailing list