generic-library/libzmq
1
0
Fork 0
mirror of https://github.com/zeromq/libzmq.git synced 2024-12-13 10:52:56 +01:00
Code Issues Projects Releases Wiki Activity

Problem: ZMQ_SERVER man page is wrong

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

Solution: fix it.
This commit is contained in:
Pieter Hintjens 2016-04-04 13:13:27 +02:00
parent e70e39be49
commit 9eb74d4df4
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/zmq_socket.txt
View File

@ -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