From 7c9b09bc511236c8cc5f6cea7623a8b98fedf302 Mon Sep 17 00:00:00 2001 From: Martin Lucina Date: Wed, 2 Jun 2010 18:36:34 +0200 Subject: Documentation: Flow control, zmq_socket(3) Mostly Flow control and additions to zmq_socket(3) Removed/changed lots of text regarding message queues More fixes for 2.0.7 changes --- doc/zmq_send.txt | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'doc/zmq_send.txt') diff --git a/doc/zmq_send.txt b/doc/zmq_send.txt index 300f812..419e386 100644 --- a/doc/zmq_send.txt +++ b/doc/zmq_send.txt @@ -20,8 +20,8 @@ argument to be sent to the socket referenced by the 'socket' argument. The *ZMQ_NOBLOCK*:: Specifies that the operation should be performed in non-blocking mode. If the -message cannot be queued on the underlying _message queue_ associated with -'socket', the _zmq_send()_ function shall fail with 'errno' set to EAGAIN. +message cannot be queued on the 'socket', the _zmq_send()_ function shall fail +with 'errno' set to EAGAIN. *ZMQ_SNDMORE*:: Specifies that the message being sent is a multi-part message, and that further @@ -30,8 +30,7 @@ below for a detailed description. NOTE: A successful invocation of _zmq_send()_ does not indicate that the message has been transmitted to the network, only that it has been queued on -the _message queue_ associated with the socket and 0MQ has assumed -responsibility for the message. +the 'socket' and 0MQ has assumed responsibility for the message. Multi-part messages @@ -60,7 +59,7 @@ return `-1` and set 'errno' to one of the values defined below. ERRORS ------ *EAGAIN*:: -Non-blocking mode was requested and the message cannot be queued at the moment. +Non-blocking mode was requested and the message cannot be sent at the moment. *ENOTSUP*:: The _zmq_send()_ operation is not supported by this socket type. *EFSM*:: -- cgit v1.2.3