zmq_connect.txt in rbczmq-1.7.2

- old
+ new

@@ -39,16 +39,18 @@
 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.
 
-NOTE: following a _zmq_connect()_, the socket enters its normal 'ready' state.
-By contrast, following a _zmq_bind()_ alone, the socket enters a 'mute' state
-in which the socket blocks or drops messages according to the socket type, as
-defined in linkzmq:zmq_socket[3].
+NOTE: following a _zmq_connect()_, for socket types except for ZMQ_ROUTER,
+the socket enters its normal 'ready' state. By contrast, following a
+_zmq_bind()_ alone, the socket enters a 'mute' state in which the socket
+blocks or drops messages according to the socket type, as defined in
+linkzmq:zmq_socket[3]. A ZMQ_ROUTER socket enters its normal 'ready' state
+for a specific peer only when handshaking is complete for that peer, which
+may take an arbitrary time.
 
-
 RETURN VALUE
 ------------
 The _zmq_connect()_ function returns zero if successful. Otherwise it returns
 `-1` and sets 'errno' to one of the values defined below.
 
@@ -92,7 +94,7 @@
 linkzmq:zmq[7]
 
 
 AUTHORS
 -------
-This 0MQ manual page was written by Pieter Hintjens <ph@imatix.com>,
-Martin Sustrik <sustrik@250bpm.com> and Martin Lucina <mato@kotelna.sk>.
+This page was written by the 0MQ community. To make a change please
+read the 0MQ Contribution Policy at <http://www.zeromq.org/docs:contributing>.