[zeromq-dev] Stopping zmq_device

[Brian Buchanan]

On Jul 9, 2010, at 12:17 , Jarred Ward wrote:
> 
> I think that forcibly releasing a blocking recv on a single thread from another thread with a socket interrupt makes the most sense. I think the recv should return an EIR (interrupt request) signalling that it was interrupted and the socket should remain usable afterward.
> 
> Thoughts?

For the Ruby extension, it is also very desirable to have the ability to interrupt a blocking call on a socket.  Ruby 1.9's API for blocking operations includes a callback that is invoked when the thread is to be interrupted/terminated (by another Ruby thread, or by Ctrl-C, or a signal handler...), but currently I can't implement this callback without turning all 0MQ calls into zmq_poll() calls and using my own notifier fd for each socket (ugly!)

So, it would be nice to have something like zmq_interrupt(socket) or zmq_abort(socket) that would cause any outstanding blocking calls on that socket to be resumed with errno = EINTR.

- Brian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20100709/54ddee02/attachment.htm>