diff options
| author | sustrik <sustrik@250bpm.com> | 2011-11-04 02:15:37 -0700 |
|---|---|---|
| committer | sustrik <sustrik@250bpm.com> | 2011-11-04 02:15:37 -0700 |
| commit | 6cdd720400ea456ccbfdf09cdc5054ab07dbdc6f (patch) | |
| tree | 6a25ede64ac1252e022feb91b1342cdc38e3dcf5 /doc/zmq_recvmsg.txt | |
| parent | 541b83bc02784c721efa3d9dde8f8a191c3c3b7b (diff) | |
| parent | e9c3a227a7175b4eda5193b1c8ce6985f5ed89f3 (diff) | |
Merge pull request #220 from 250bpm/HEAD
Refactoring
Diffstat (limited to 'doc/zmq_recvmsg.txt')
| -rw-r--r-- | doc/zmq_recvmsg.txt | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/doc/zmq_recvmsg.txt b/doc/zmq_recvmsg.txt index 358ea3f..6e41b1e 100644 --- a/doc/zmq_recvmsg.txt +++ b/doc/zmq_recvmsg.txt @@ -29,8 +29,7 @@ function shall fail with 'errno' set to EAGAIN. Multi-part messages ~~~~~~~~~~~~~~~~~~~ -A 0MQ message is composed of 1 or more message parts, starting with zero or -more address 'label' parts, followed by 1 or more 'data' parts. Each message +A 0MQ message is composed of 1 or more message parts. Each message part is an independent 'zmq_msg_t' in its own right. 0MQ ensures atomic delivery of messages; peers shall receive either all _message parts_ of a message or none at all. The total number of message parts is unlimited except @@ -38,9 +37,7 @@ by available memory. An application that processes multipart messages must use the _ZMQ_RCVMORE_ linkzmq:zmq_getsockopt[3] option after calling _zmq_recvmsg()_ to determine if -there are further parts to receive. An application that manipulates address -labels must use _ZMQ_RCVLABEL_ to determine the zero or more label parts -that precede the data part(s). +there are further parts to receive. RETURN VALUE |