WIP: Socket migration between threads, new zmq_close() semantics

Sockets may now be migrated between OS threads; sockets may not be used by
more than one thread at any time. To migrate a socket to another thread the
caller must ensure that a full memory barrier is called before using the
socket from the target thread.

The new zmq_close() semantics implement the behaviour discussed at:

http://lists.zeromq.org/pipermail/zeromq-dev/2010-July/004244.html

Specifically, zmq_close() is now deterministic and while it still returns
immediately, it does not discard any data that may still be queued for
sending. Further, zmq_term() will now block until all outstanding data has
been sent.

TODO: Many bugs have been introduced, needs testing. Further, SO_LINGER or
an equivalent mechanism (possibly a configurable timeout to zmq_term())
needs to be implemented.

1 files changed, 9 insertions, 4 deletions

diff --git a/src/lb.hpp b/src/lb.hpp
index 526a727..e69385e 100644
--- a/src/lb.hpp
+++ b/src/lb.hpp
@@ -21,25 +21,30 @@
 #define __ZMQ_LB_HPP_INCLUDED__
 
 #include "yarray.hpp"
+#include "pipe.hpp"
 
 namespace zmq
 {
 
     //  Class manages a set of outbound pipes. On send it load balances
     //  messages fairly among the pipes.
-    class lb_t
+    class lb_t : public i_writer_events
     {
     public:
 
         lb_t ();
         ~lb_t ();
 
-        void attach (class writer_t *pipe_);
-        void detach (class writer_t *pipe_);
-        void revive (class writer_t *pipe_);
+        void attach (writer_t *pipe_);
+        void term_pipes ();
+        bool has_pipes ();
         int send (zmq_msg_t *msg_, int flags_);
         bool has_out ();
 
+        //  i_writer_events interface implementation.
+        void activated (writer_t *pipe_);
+        void terminated (writer_t *pipe_);
+
     private:
 
         //  List of outbound pipes.