From f86264db3ea2385783ee044b07ab0323f70788b7 Mon Sep 17 00:00:00 2001 From: Floris Bruynooghe Date: Thu, 27 Aug 2015 10:40:21 +0100 Subject: [PATCH] Update zmq_inproc manpage for bind/connect order The order of zmq_bind() and zmq_connect() is no longer important for the inproc transport since libzmq 4.0. This updates this in the zmq_inproc manpage. --- doc/zmq_inproc.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/zmq_inproc.txt b/doc/zmq_inproc.txt index 34e7dcda..feb449df 100644 --- a/doc/zmq_inproc.txt +++ b/doc/zmq_inproc.txt @@ -41,9 +41,11 @@ Connecting a socket ~~~~~~~~~~~~~~~~~~~ When connecting a 'socket' to a peer address using _zmq_connect()_ with the 'inproc' transport, the 'endpoint' shall be interpreted as an arbitrary string -identifying the 'name' to connect to. The 'name' must have been previously -created by assigning it to at least one 'socket' within the same 0MQ 'context' -as the 'socket' being connected. +identifying the 'name' to connect to. Before version 4.0 he 'name' must have +been previously created by assigning it to at least one 'socket' within the +same 0MQ 'context' as the 'socket' being connected. Since version 4.0 the +order of _zmq_bind()_ and _zmq_connect()_ does not matter just like for the tcp +transport type. EXAMPLES