diff options
author | Martin Sustrik <sustrik@fastmq.commkdir> | 2010-01-14 14:11:34 +0100 |
---|---|---|
committer | Martin Sustrik <sustrik@fastmq.commkdir> | 2010-01-14 14:11:34 +0100 |
commit | b60342ae1a95dbb303705f5b89a94b33805a3841 (patch) | |
tree | 830581b7c557e16a5aa951dbe5e77434b901cb3f /man/man3 | |
parent | 067ba3b9f77a253d4ce58e05ef1fa7702c32b2a3 (diff) |
man pages are more specific on NIC name issue
Diffstat (limited to 'man/man3')
-rw-r--r-- | man/man3/zmq_bind.3 | 12 | ||||
-rw-r--r-- | man/man3/zmq_connect.3 | 12 |
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 |