From 544b36da68729daffefa8f40d2efed5945851a01 Mon Sep 17 00:00:00 2001
From: Martin Lucina <mato@kotelna.sk>
Date: Fri, 30 Jul 2010 16:49:06 +0200
Subject: 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.
---
 src/xreq.hpp | 3 ---
 1 file changed, 3 deletions(-)

(limited to 'src/xreq.hpp')

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&);
     };
-- 
cgit v1.2.3