summaryrefslogtreecommitdiff
path: root/doc/zmq.txt
diff options
context:
space:
mode:
authorPieter Hintjens <ph@imatix.com>2010-08-04 16:05:25 +0200
committerPieter Hintjens <ph@imatix.com>2010-08-04 16:05:25 +0200
commit13f3481e127a6b2390e847af6b01ee88f1b4ae61 (patch)
tree68a584ef6f3a9eed707df5bca7cbdb339c3c546e /doc/zmq.txt
parent6ff193999d96487f7aa7e578980ab5554e61d8dc (diff)
Further cleanups on reference manual
- fixed unwrapped text in new man pages - fixed over-long lines in older pages, where possible - removed reference to old standalong devices from index page - added refernce to new zmq_device[3] documented from index page - some minor spelling corrections
Diffstat (limited to 'doc/zmq.txt')
-rw-r--r--doc/zmq.txt22
1 files changed, 8 insertions, 14 deletions
diff --git a/doc/zmq.txt b/doc/zmq.txt
index e8a3a97..0ff26e7 100644
--- a/doc/zmq.txt
+++ b/doc/zmq.txt
@@ -140,20 +140,14 @@ Local in-process (inter-thread) communication transport::
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]
+0MQ provides 'devices', which are building blocks that act as intermediate
+nodes in complex messaging topologies. Devices can act as brokers that other
+nodes connect to, proxies that connect through to other nodes, or any mix of
+these two models.
+
+You can start a device in an application thread, see linkzmq:zmq_device[3],
+and you can also start devices externally, as standalone processes, see
+linkzmq:zmq_deviced[1].
ERROR HANDLING