diff options
author | Martin Lucina <mato@kotelna.sk> | 2010-06-02 18:36:34 +0200 |
---|---|---|
committer | Martin Lucina <mato@kotelna.sk> | 2010-06-02 18:36:34 +0200 |
commit | 7c9b09bc511236c8cc5f6cea7623a8b98fedf302 (patch) | |
tree | 1a2f6be6ef87fb4a21c4ace9b36df0f3c06d0e6c /doc/zmq.txt | |
parent | 9d00d300b0d6b45d2954792540cc95a0c3fb6a01 (diff) |
Documentation: Flow control, zmq_socket(3)
Mostly Flow control and additions to zmq_socket(3)
Removed/changed lots of text regarding message queues
More fixes for 2.0.7 changes
Diffstat (limited to 'doc/zmq.txt')
-rw-r--r-- | doc/zmq.txt | 18 |
1 files changed, 4 insertions, 14 deletions
diff --git a/doc/zmq.txt b/doc/zmq.txt index fd9f7ed..2d7f1c8 100644 --- a/doc/zmq.txt +++ b/doc/zmq.txt @@ -86,17 +86,9 @@ Message manipulation:: Sockets ~~~~~~~ -Standard sockets present a _synchronous_ interface to either connection-mode -reliable byte streams (SOCK_STREAM), or connection-less unreliable datagrams -(SOCK_DGRAM). In comparison, 0MQ sockets present an abstraction of a -asynchronous _message queue_, with the exact queueing semantics depending on -the socket type in use. See linkzmq:zmq_socket[3] for the socket types -provided. - -0MQ sockets being _asynchronous_ means that the timings of the physical -connection setup and teardown, reconnect and effective delivery are organized -by 0MQ itself, and that messages may be _queued_ in the event that a peer is -unavailable to receive them. +0MQ sockets present an abstraction of a asynchronous _message queue_, with the +exact queueing semantics depending on the socket type in use. See +linkzmq:zmq_socket[3] for the socket types provided. The following functions are provided to work with sockets: @@ -118,9 +110,7 @@ Sending and receiving messages:: linkzmq:zmq_send[3] linkzmq:zmq_recv[3] - -Input/output multiplexing -^^^^^^^^^^^^^^^^^^^^^^^^^ +.Input/output multiplexing 0MQ provides a mechanism for applications to multiplex input/output events over a set containing both 0MQ sockets and standard sockets. This mechanism mirrors the standard _poll()_ system call, and is described in detail in |