ZMQII-65: Two OS threads are mapped to the same app_thread_t

1 files changed, 0 insertions, 19 deletions

diff --git a/src/app_thread.hpp b/src/app_thread.hpp
index 0e2c3e1..9bd5641 100644
--- a/src/app_thread.hpp
+++ b/src/app_thread.hpp
@@ -25,7 +25,6 @@
 #include "stdint.hpp"
 #include "object.hpp"
 #include "yarray.hpp"
-#include "thread.hpp"
 
 namespace zmq
 {
@@ -42,17 +41,6 @@ namespace zmq
         //  Returns signaler associated with this application thread.
         struct i_signaler *get_signaler ();
 
-        //  Nota bene: Following two functions are accessed from different
-        //  threads. The caller (dispatcher) is responsible for synchronisation
-        //  of accesses.
-
-        //  Returns true is current thread is associated with the app thread.
-        bool is_current ();
-
-        //  Tries to associate current thread with the app thread object.
-        //  Returns true is successfull, false otherwise.
-        bool make_current ();
-
         //  Processes commands sent to this thread (if any). If 'block' is
         //  set to true, returns only after at least one command was processed.
         //  If throttle argument is true, commands are processed at most once
@@ -71,13 +59,6 @@ namespace zmq
         typedef yarray_t <socket_base_t> sockets_t;
         sockets_t sockets;
 
-        //  If false, app_thread_t object is not associated with any OS thread.
-        //  In such case, 'tid' member contains a bogus value.
-        bool associated;
-
-        //  Thread ID associated with this slot.
-        thread_t::id_t tid;
-
         //  App thread's signaler object.
         struct i_signaler *signaler;