diff options
author | Martin Lucina <mato@kotelna.sk> | 2010-07-30 16:49:06 +0200 |
---|---|---|
committer | Martin Lucina <mato@kotelna.sk> | 2010-07-30 16:49:06 +0200 |
commit | 544b36da68729daffefa8f40d2efed5945851a01 (patch) | |
tree | 00af12f26dd5c1986f625726c8938b80c83af2af /src/xreq.hpp | |
parent | 66470b2c55d74fb137211f4264bbfc5e3f454534 (diff) |
XREQ: Correct behaviour on hitting ZMQ_HWM
This reverts part of commit 84e0c7991a9b316ed571533abc628cc1175750a3 to get
correct ZMQ_HWM semantics with XREQ sockets:
When sending a message to an XREQ socket, the underlying pipe is selected in
a round-robin fashion. If an underlying pipe is full it is skipped. If there
are no underlying pipes, or all underlying pipes are full then zmq_send()
shall block or return EAGAIN, depending on whether or not the call is blocking.
Messages are never dropped.
Diffstat (limited to 'src/xreq.hpp')
-rw-r--r-- | src/xreq.hpp | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/xreq.hpp b/src/xreq.hpp index 25a97f1..8ee0bb9 100644 --- a/src/xreq.hpp +++ b/src/xreq.hpp @@ -55,9 +55,6 @@ namespace zmq fq_t fq; lb_t lb; - // If true, curently sent message is being dropped. - bool dropping; - xreq_t (const xreq_t&); void operator = (const xreq_t&); }; |