summaryrefslogtreecommitdiff
path: root/man/man3
diff options
context:
space:
mode:
authorunknown <bundra@.(none)>2010-01-14 15:50:54 +0100
committerunknown <bundra@.(none)>2010-01-14 15:50:54 +0100
commit56c369272c279224562d11b0a66590ac7826f4f3 (patch)
treeab9175eae8c5a007deadc59f11c7a78f37302a21 /man/man3
parentb9b0124d553b30932d8b78fb774ae258fa0d0f4d (diff)
parentb60342ae1a95dbb303705f5b89a94b33805a3841 (diff)
Merge branch 'master' of github.com:sustrik/zeromq2
Diffstat (limited to 'man/man3')
-rw-r--r--man/man3/zmq_bind.312
-rw-r--r--man/man3/zmq_connect.312
2 files changed, 16 insertions, 8 deletions
diff --git a/man/man3/zmq_bind.3 b/man/man3/zmq_bind.3
index c4d955e..b8f2102 100644
--- a/man/man3/zmq_bind.3
+++ b/man/man3/zmq_bind.3
@@ -5,16 +5,20 @@ zmq_bind \- binds the socket to the specified address
.B int zmq_bind (void *s, const char *addr);
.SH DESCRIPTION
The function binds socket
-.IR s to a particular transport. Actual semantics of the
+.IR s
+to a particular transport. Actual semantics of the
command depend on the underlying transport mechanism, however, in cases where
peers connect in an asymetric manner,
.IR zmq_bind
should be called first,
.IR zmq_connect
-afterwards. For actual formats of
+afterwards. Actual formats of
.IR addr
-parameter for different types of transport have a look at
-.IR zmq(7) .
+parameter are defined by individual transports. For a list of supported
+transports have a look at
+.IR zmq(7)
+manual page.
+
Note that single socket can be bound (and connected) to
arbitrary number of peers using different transport mechanisms.
.SH RETURN VALUE
diff --git a/man/man3/zmq_connect.3 b/man/man3/zmq_connect.3
index 291d113..dd0b5d8 100644
--- a/man/man3/zmq_connect.3
+++ b/man/man3/zmq_connect.3
@@ -5,17 +5,21 @@ zmq_connect \- connect the socket to the specified peer
.B int zmq_connect (void *s, const char *addr);
.SH DESCRIPTION
The function connect socket
-.IR s to the peer identified by
+.IR s
+to the peer identified by
.IR addr .
Actual semantics of the command depend on the underlying transport mechanism,
however, in cases where peers connect in an asymetric manner,
.IR zmq_bind
should be called first,
.IR zmq_connect
-afterwards. For actual formats of
+afterwards. Formats of the
.IR addr
-parameter for different types of transport have a look at
-.IR zmq(7) .
+parameter are defined by individual transports. For a list of supported
+transports have a look at
+.IR zmq(7)
+manual page.
+
Note that single socket can be connected (and bound) to
arbitrary number of peers using different transport mechanisms.
.SH RETURN VALUE