Skip to content

L
libzmq
Commit c85ecfc0 authored by Pieter Hintjens's avatar Pieter Hintjens
Browse files
Options

Cleaned up description of multi-part messages

parent 636de46f
Hide whitespace changes
Inline Side-by-side
Showing with 19 additions and 22 deletions
doc/zmq_recv.txt
View file @ c85ecfc0
...@@ -29,13 +29,12 @@ function shall fail with 'errno' set to EAGAIN. ...@@ -29,13 +29,12 @@ function shall fail with 'errno' set to EAGAIN.
Multi-part messages Multi-part messages
~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
A 0MQ message is composed of 1 or more message parts. Each message A 0MQ message is composed of 1 or more message parts. 0MQ ensures atomic
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
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 message or none at all. The total number of message parts is unlimited except
by available memory. by available memory.
An application that processes multipart messages must use the _ZMQ_RCVMORE_ An application that processes multi-part messages must use the _ZMQ_RCVMORE_
linkzmq:zmq_getsockopt[3] option after calling _zmq_recv()_ to determine if linkzmq:zmq_getsockopt[3] option after calling _zmq_recv()_ to determine if
there are further parts to receive. there are further parts to receive.
...@@ -89,6 +88,6 @@ linkzmq:zmq[7] ...@@ -89,6 +88,6 @@ linkzmq:zmq[7]
AUTHORS AUTHORS
------- -------
+This man page was written by Martin Sustrik <sustrik@250bpm.com>, Martin This 0MQ manual page was written by Martin Sustrik <sustrik@250bpm.com> and
+Lucina <martin@lucina.net> and Pieter Hintjens <ph@imatix.com>. Martin Lucina <mato@kotelna.sk>, and Pieter Hintjens <ph@imatix.com>.
doc/zmq_recvmsg.txt
View file @ c85ecfc0
...@@ -31,11 +31,11 @@ Multi-part messages ...@@ -31,11 +31,11 @@ Multi-part messages
~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
A 0MQ message is composed of 1 or more message 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 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 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 message or none at all. The total number of message parts is unlimited except
by available memory. by available memory.
An application that processes multipart messages must use the _ZMQ_RCVMORE_ An application that processes multi-part messages must use the _ZMQ_RCVMORE_
linkzmq:zmq_getsockopt[3] option after calling _zmq_recvmsg()_ to determine if linkzmq:zmq_getsockopt[3] option after calling _zmq_recvmsg()_ to determine if
there are further parts to receive. there are further parts to receive.
......
doc/zmq_send.txt
View file @ c85ecfc0
...@@ -4,7 +4,7 @@ zmq_send(3) ...@@ -4,7 +4,7 @@ zmq_send(3)
NAME NAME
---- ----
zmq_send - send a message part on a socket zmq_send - send a message part on a socket
SYNOPSIS SYNOPSIS
...@@ -35,14 +35,13 @@ the 'socket' and 0MQ has assumed responsibility for the message. ...@@ -35,14 +35,13 @@ the 'socket' and 0MQ has assumed responsibility for the message.
Multi-part messages Multi-part messages
~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
A 0MQ message is composed of 1 or more message parts. Each message A 0MQ message is composed of 1 or more message parts. 0MQ ensures atomic
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
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 message or none at all. The total number of message parts is unlimited except
by available memory. by available memory.
An application that sends multipart messages must use the _ZMQ_SNDMORE_ flag An application that sends multi-part messages must use the _ZMQ_SNDMORE_ flag
when sending each data part except the final one. when sending each message part except the final one.
RETURN VALUE RETURN VALUE
...@@ -100,6 +99,5 @@ linkzmq:zmq[7] ...@@ -100,6 +99,5 @@ linkzmq:zmq[7]
AUTHORS AUTHORS
------- -------
+This man page was written by Martin Sustrik <sustrik@250bpm.com>, Martin This 0MQ manual page was written by Martin Sustrik <sustrik@250bpm.com> and
+Lucina <martin@lucina.net> and Pieter Hintjens <ph@imatix.com>. Martin Lucina <mato@kotelna.sk>, and Pieter Hintjens <ph@imatix.com>.
doc/zmq_sendmsg.txt
View file @ c85ecfc0
...@@ -41,12 +41,12 @@ Multi-part messages ...@@ -41,12 +41,12 @@ Multi-part messages
~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
A 0MQ message is composed of 1 or more message 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 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 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 message or none at all. The total number of message parts is unlimited except
by available memory. by available memory.
An application that sends multipart messages must use the _ZMQ_SNDMORE_ flag An application that sends multi-part messages must use the _ZMQ_SNDMORE_ flag
when sending each data part except the final one. when sending each message part except the final one.
RETURN VALUE RETURN VALUE
------------ ------------
...@@ -116,6 +116,6 @@ linkzmq:zmq[7] ...@@ -116,6 +116,6 @@ linkzmq:zmq[7]
AUTHORS AUTHORS
------- -------
+This man page was written by Martin Sustrik <sustrik@250bpm.com>, Martin This 0MQ manual page was written by Martin Sustrik <sustrik@250bpm.com> and
+Lucina <martin@lucina.net> and Pieter Hintjens <ph@imatix.com>. Martin Lucina <mato@kotelna.sk>, and Pieter Hintjens <ph@imatix.com>.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment