Problem: thread safety documentation is misleading

Solution: change it to categorically state that non-thread-safe
sockets are not thread safe, ever
This commit is contained in:
Luca Boccassi 2020-06-09 10:25:18 +01:00
parent 7c3eaf864c
commit 7f83eeb1b7

View File

@ -49,8 +49,8 @@ _zmq_bind()_, thus allowing many-to-many relationships.
.Thread safety .Thread safety
0MQ has both thread safe socket type and _not_ thread safe socket types. 0MQ has both thread safe socket type and _not_ thread safe socket types.
Applications MUST NOT use a _not_ thread safe socket Applications MUST NOT use a _not_ thread safe socket
from multiple threads except after migrating a socket from one thread to from multiple threads under any circumstances. Doing so results in undefined
another with a "full fence" memory barrier. behaviour.
Following are the thread safe sockets: Following are the thread safe sockets:
* ZMQ_CLIENT * ZMQ_CLIENT