Commit 39b87335 authored by Christian Fibich's avatar Christian Fibich
Browse files


parent d71b6291
......@@ -62,7 +62,7 @@ of the following parts in this order:
2. A message providing further details on the completion status in
a *non-terminated* string
*non-terminated* means that the trailing `\0` byte is not transmitted
via ZeroMQ.
......@@ -70,7 +70,7 @@ via ZeroMQ.
You may use the functions in `common/zmq_strings.c` to send/receive
conventional C strings via ZeroMQ
Multi-part messages can be *sent* by supplying the `ZMQ_SNDMORE` to
the [`zmq_send(3)`]( and [`zmq_msg_send(3)`]( functions in all but the last
......@@ -84,7 +84,7 @@ message, use
* or [`zmq_getsockopt(3)`]( on the socket with the `ZMQ_RCVMORE` option name if using [`zmq_recv(3)`](
You can read/write to a ZeroMQ socket directly from a buffer (e.g., an array) via
[`zmq_recv(3)`]([`zmq_send(3)`]( or via ZeroMQ message objects using [`zmq_msg_recv(3)`]([`zmq_msg_send(3)`](
......@@ -107,13 +107,13 @@ server.
It may subscribe to one or more channels, which shall be passed as
command-line arguments.
Subscribing to a particular prefix is done by calling [`zmq_setsockopt(3)`](
on the socket with `ZMQ_SUBSCRIBE` as _option name_ and the prefix data
(in this case, the channel name) as _option value_.
To prevent that a subscriber subscribed to channel _cat_ also
receives messages from channel _catastrophes_ (due to the common prefix _cat_),
Supports Markdown
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