From eb0e0dda4e8103ea38080406436285adb9be2fe9 Mon Sep 17 00:00:00 2001 From: WGH Date: Mon, 3 Oct 2016 23:39:34 +0300 Subject: [PATCH] doc/zmq_socket.txt: clarify that ROUTER can be blocking --- doc/zmq_socket.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/zmq_socket.txt b/doc/zmq_socket.txt index d9f7733f..c5fb43a4 100644 --- a/doc/zmq_socket.txt +++ b/doc/zmq_socket.txt @@ -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