Skip to content

Commit

Permalink
Problem: ZMQ_SERVER man page is wrong
Browse files Browse the repository at this point in the history
It says that ZMQ_SERVER never blocks; whereas it does block on
sending to a client whose pipe is full.

Solution: fix it.
  • Loading branch information
hintjens committed Apr 4, 2016
1 parent e70e39b commit 9eb74d4
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions doc/zmq_socket.txt
Original file line number Diff line number Diff line change
Expand Up @@ -121,8 +121,9 @@ a message to a given 'ZMQ_CLIENT' peer the application must set the peer's

If the 'routing_id' is not specified, or does not refer to a connected client
peer, the send call will fail with EHOSTUNREACH. If the outgoing buffer for
the client peer is full, the send call will fail with EAGAIN. The 'ZMQ_SERVER'
socket shall not drop messages, nor shall it block.
the client peer is full, the send call shall block, unless ZMQ_DONT_WAIT is
used in the send, in which case it shall fail with EAGAIN. The 'ZMQ_SERVER'
socket shall not drop messages in any case.

NOTE: 'ZMQ_SERVER' sockets are threadsafe. They do not accept the ZMQ_SNDMORE
option on sends not ZMQ_RCVMORE on receives. This limits them to single part
Expand Down

0 comments on commit 9eb74d4

Please sign in to comment.