From 1b733e75a26cbf9f9c31e8f045efcc1d738223aa Mon Sep 17 00:00:00 2001 From: Luca Boccassi Date: Wed, 21 Mar 2018 19:57:54 +0000 Subject: [PATCH] Problem: zmq_connect doc says inproc has to be bound first Solution: fix it, as since 4.2.0 there is no ordering constraint anymore Fixes: #2854 --- doc/zmq_connect.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/zmq_connect.txt b/doc/zmq_connect.txt index 01069c22..398d20e1 100644 --- a/doc/zmq_connect.txt +++ b/doc/zmq_connect.txt @@ -38,9 +38,8 @@ immediately but as needed by 0MQ. Thus a successful call to _zmq_connect()_ does not mean that the connection was or could actually be established. Because of this, for most transports and socket types the order in which a 'server' socket is bound and a 'client' socket is connected to it does not -matter. The first exception is when using the inproc:// transport: you must -call _zmq_bind()_ before calling _zmq_connect()_. The second exception are -_ZMQ_PAIR_ sockets, which do not automatically reconnect to endpoints. +matter. The _ZMQ_PAIR_ sockets are an exception, as they do not automatically +reconnect to endpoints. NOTE: following a _zmq_connect()_, for socket types except for ZMQ_ROUTER, the socket enters its normal 'ready' state. By contrast, following a