[zeromq-dev] differences in polling between device and non device fd's
I'm using a jruby gem that has it's own reactor, and monitors zeromq file descriptors so you can send messages to the reactor via zeromq. I'm running into a strange issue where the reactor is not getting events from the fd. It gets a couple then no more. This happens to me when using the queue device, but not when I just use req/rep or push/pull. Is there anything different about how devices monitor file descriptors that could cause issues for external code that is monitoring them? At this point I'm assuming it's a bug in the jruby gem, but it would be helpful to know if devices do something different in this area before I go hacking on the jruby code. Anyone have any insight into this? Chris ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] differences in polling between device and non device fd's
On 17/02/2012, at 7:41 AM, snacktime wrote: I'm using a jruby gem that has it's own reactor, and monitors zeromq file descriptors so you can send messages to the reactor via zeromq. I'm running into a strange issue where the reactor is not getting events from the fd. It gets a couple then no more. This happens to me when using the queue device, but not when I just use req/rep or push/pull. Is there anything different about how devices monitor file descriptors that could cause issues for external code that is monitoring them? The queue device is using zmq_poll, which in turn is calling select or whatever. If you're also polling the same files it can't work. It should work if you're polling different ones. HTH -- john skaller skal...@users.sourceforge.net ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
