Commit 636de46f authored by Pieter Hintjens's avatar Pieter Hintjens

Removed section on devices, added new methods

parent 086c0594
......@@ -84,6 +84,9 @@ Access message content::
linkzmq:zmq_msg_data[3]
linkzmq:zmq_msg_size[3]
Get message properties::
linkzmq:zmq_getmsgopt[3]
Message manipulation::
linkzmq:zmq_msg_copy[3]
linkzmq:zmq_msg_move[3]
......@@ -113,7 +116,9 @@ Establishing a message flow::
Sending and receiving messages::
linkzmq:zmq_send[3]
linkzmq:zmq_sendmsg[3]
linkzmq:zmq_recv[3]
linkzmq:zmq_recvmsg[3]
.Input/output multiplexing
0MQ provides a mechanism for applications to multiplex input/output events over
......@@ -143,24 +148,6 @@ Local in-process (inter-thread) communication transport::
linkzmq:zmq_inproc[7]
Devices
~~~~~~~
Apart from the 0MQ library the 0MQ distribution includes 'devices' which are
building blocks intended to serve as intermediate nodes in complex messaging
topologies.
The following devices are provided:
Forwarder device for request-response messaging::
linkzmq:zmq_queue[1]
Forwarder device for publish-subscribe messaging::
linkzmq:zmq_forwarder[1]
Streamer device for parallelized pipeline messaging::
linkzmq:zmq_streamer[1]
ERROR HANDLING
--------------
The 0MQ library functions handle errors using the standard conventions found on
......
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