Commit 9eb74d4d authored by Pieter Hintjens's avatar Pieter Hintjens

Problem: ZMQ_SERVER man page is wrong

It says that ZMQ_SERVER never blocks; whereas it does block on
sending to a client whose pipe is full.

Solution: fix it.
parent e70e39be
...@@ -121,8 +121,9 @@ a message to a given 'ZMQ_CLIENT' peer the application must set the peer's ...@@ -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 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 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' the client peer is full, the send call shall block, unless ZMQ_DONT_WAIT is
socket shall not drop messages, nor shall it block. 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 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 option on sends not ZMQ_RCVMORE on receives. This limits them to single part
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment