diff options
| author | Martin Lucina <mato@kotelna.sk> | 2010-05-28 00:49:13 +0200 |
|---|---|---|
| committer | Martin Lucina <mato@kotelna.sk> | 2010-05-28 00:49:13 +0200 |
| commit | 5219e4ce8f9aa082c5f91e248a9f66639c69727d (patch) | |
| tree | c5ebc761b631e44f1b2047ba39761b8fefc8770a /doc/zmq.txt | |
| parent | 8408ae066dce123fc93e4f53dbadb1f60b7f2e8a (diff) | |
Clarify socket types in documentation, reinstate ZMQ_PAIR
Diffstat (limited to 'doc/zmq.txt')
| -rw-r--r-- | doc/zmq.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/zmq.txt b/doc/zmq.txt index 003570a..fa15e43 100644 --- a/doc/zmq.txt +++ b/doc/zmq.txt @@ -90,8 +90,8 @@ 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 (_messaging pattern_) in use. See linkzmq:zmq_socket[3] for the -_messaging patterns_ provided. +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 |