[zeromq-dev] Fwd: ZMQ Closure - Change of Beginners Documentation

Pieter Hintjens ph at imatix.com
Thu May 26 19:03:06 CEST 2011

On Thu, May 26, 2011 at 3:06 AM, Mike Pearce <mike at kaew.be> wrote:

> I would like that this section of the guide have the following added -
> 1. It states that the socket functions are not thread safe and so anyone
> implementing a multithreaded application solution must adhere to this.

This is covered in the section on multithreading. Like I said, I'm
more than happy to repeat that earlier on, since people do seem to
keep making the assumption that threads can share sockets.

> 2. It states that if the users application is doing a blocking read then
> zmq_term is the means by which this blocked read will get unblocked. By
> implication an application that implements a blocked read will need to be
> multithreaded.

This isn't accurate, though. A classic way of exiting a blocked read
is to receive a message, or to be interrupted by a signal like SIGINT.


More information about the zeromq-dev mailing list