Merge pull request #2148 from WGH-/doc-router-mandatory-block

doc/zmq_socket.txt: clarify that ROUTER can be blocking
This commit is contained in:
Luca Boccassi 2016-10-03 22:21:38 +01:00 committed by GitHub
commit 075dd6a003

View File

@ -510,7 +510,8 @@ socket option is set to '1'.
When a 'ZMQ_ROUTER' socket enters the 'mute' state due to having reached the
high water mark for all peers, then any messages sent to the socket shall be dropped
until the mute state ends. Likewise, any messages routed to a peer for which
the individual high water mark has been reached shall also be dropped.
the individual high water mark has been reached shall also be dropped,
unless 'ZMQ_ROUTER_MANDATORY' socket option is set.
When a 'ZMQ_REQ' socket is connected to a 'ZMQ_ROUTER' socket, in addition to the
_identity_ of the originating peer each message received shall contain an empty
@ -526,7 +527,7 @@ Direction:: Bidirectional
Send/receive pattern:: Unrestricted
Outgoing routing strategy:: See text
Incoming routing strategy:: Fair-queued
Action in mute state:: Drop
Action in mute state:: Drop (see text)
RETURN VALUE