From 884c7f78e984f99389a9cd3ed3784b56452c5fa0 Mon Sep 17 00:00:00 2001 From: Pieter Hintjens Date: Tue, 9 Feb 2016 09:57:07 +0100 Subject: [PATCH] Problem: zmq_getsockopt wrongly referred to ZMQ_THREADSAFE The proper name is ZMQ_THREAD_SAFE Solution: fix in the documentation. --- doc/zmq_getsockopt.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/zmq_getsockopt.txt b/doc/zmq_getsockopt.txt index 9293bc9b..3989eb52 100644 --- a/doc/zmq_getsockopt.txt +++ b/doc/zmq_getsockopt.txt @@ -715,9 +715,9 @@ Default value:: 0 (leave to OS default) Applicable socket types:: all, when using TCP transports. -ZMQ_THREADSAFE: Retrieve socket thread safety -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The 'ZMQ_THREADSAFE' option shall retrieve a boolean value indicating whether +ZMQ_THREAD_SAFE: Retrieve socket thread safety +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +The 'ZMQ_THREAD_SAFE' option shall retrieve a boolean value indicating whether or not the socket is threadsafe. Currently 'ZMQ_CLIENT' and 'ZMQ_SERVER' sockets are threadsafe.