From 7f83eeb1b7ad7beb56995465404966786569bc6e Mon Sep 17 00:00:00 2001 From: Luca Boccassi Date: Tue, 9 Jun 2020 10:25:18 +0100 Subject: [PATCH] Problem: thread safety documentation is misleading Solution: change it to categorically state that non-thread-safe sockets are not thread safe, ever --- doc/zmq_socket.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/zmq_socket.txt b/doc/zmq_socket.txt index 6f53186c..dfdbd961 100644 --- a/doc/zmq_socket.txt +++ b/doc/zmq_socket.txt @@ -49,8 +49,8 @@ _zmq_bind()_, thus allowing many-to-many relationships. .Thread safety 0MQ has both thread safe socket type and _not_ thread safe socket types. Applications MUST NOT use a _not_ thread safe socket -from multiple threads except after migrating a socket from one thread to -another with a "full fence" memory barrier. +from multiple threads under any circumstances. Doing so results in undefined +behaviour. Following are the thread safe sockets: * ZMQ_CLIENT