diff options
| author | Martin Lucina <mato@kotelna.sk> | 2010-12-07 11:10:21 +0100 |
|---|---|---|
| committer | Martin Lucina <mato@kotelna.sk> | 2010-12-07 11:10:21 +0100 |
| commit | 9bb5323a1abce0dcf8ed56734313a5249003d868 (patch) | |
| tree | 069490eca55e3b3e36c323416cc0ddb64bdf140b | |
| parent | 73bbcb552d6fbd1b3744a1ee29202a19e4d2f46e (diff) | |
Clarify zmq_send() operation for ZMQ_PUB sockets
Signed-off-by: Martin Lucina <mato@kotelna.sk>
| -rw-r--r-- | doc/zmq_socket.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/zmq_socket.txt b/doc/zmq_socket.txt index 6bcb133..7ac8fa1 100644 --- a/doc/zmq_socket.txt +++ b/doc/zmq_socket.txt @@ -190,7 +190,7 @@ The linkzmq:zmq_recv[3] function is not implemented for this socket type. When a 'ZMQ_PUB' socket enters an exceptional state due to having reached the high water mark for a _subscriber_, then any messages that would be sent to the _subscriber_ in question shall instead be dropped until the exceptional state -ends. +ends. The _zmq_send()_ function shall never block for this socket type. [horizontal] .Summary of ZMQ_PUB characteristics |