summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Sustrik <sustrik@250bpm.com>2011-04-15 08:03:26 +0200
committerMartin Sustrik <sustrik@250bpm.com>2011-04-15 08:03:26 +0200
commit452ea97f5bb1bdd4d5ba76279de4189e8b8e5662 (patch)
tree77e5cfc6db871d3e91858212c0b0a494aa3beed2
parent590ad2510bb113fdcd36951f6321fc73be94944a (diff)
zmq_send(3) manpage improved
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-rw-r--r--doc/zmq_send.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/zmq_send.txt b/doc/zmq_send.txt
index 4561ae0..2a63cc6 100644
--- a/doc/zmq_send.txt
+++ b/doc/zmq_send.txt
@@ -28,6 +28,10 @@ Specifies that the message being sent is a multi-part message, and that further
message parts are to follow. Refer to the section regarding multi-part messages
below for a detailed description.
+The _zmq_msg_t_ structure passed to _zmq_send()_ is nullified during the call.
+If you want to send the same message to multiple sockets you have to copy it
+using (e.g. using _zmq_msg_copy()_).
+
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 'socket' and 0MQ has assumed responsibility for the message.