Changeset 16727 for trunk/FACT++/src/lidctrl.cc

Timestamp:

06/05/13 20:36:57 (11 years ago)

Author:

tbretz

Message:

Make use of the new StateMachineAsio which gets the CPU consumption to basically 0 by a more intelligent event management.

File:

• trunk/FACT++/src/lidctrl.cc (modified) (5 diffs)

trunk/FACT++/src/lidctrl.cc

@@ -1 @@
-#include <boost/bind.hpp>
 #include <boost/array.hpp>
 
@@ -12 +11 @@
 #include "Event.h"
 #include "StateMachineDim.h"
+#include "StateMachineAsio.h"
 #include "Connection.h"
 #include "LocalControl.h"
@@ -460 +460 @@
 
 template <class T, class S>
-class StateMachineLidControl : public T, public ba::io_service, public ba::io_service::work
+class StateMachineLidControl : public StateMachineAsio<T>
 {
 private:
@@ -529 +529 @@
     int Execute()
     {
-        // Dispatch (execute) at most one handler from the queue. In contrary
-        // to run_one(), it doesn't wait until a handler is available
-        // which can be dispatched, so poll_one() might return with 0
-        // handlers dispatched. The handlers are always dispatched/executed
-        // synchronously, i.e. within the call to poll_one()
-        poll_one();
-
         const int rc = fLid.GetState();
 
@@ -551 +544 @@
 public:
     StateMachineLidControl(ostream &out=cout) :
-        T(out, "LID_CONTROL"), ba::io_service::work(static_cast<ba::io_service&>(*this)),
-        fLid(*this, *this)
-    {
-        // ba::io_service::work is a kind of keep_alive for the loop.
-        // It prevents the io_service to go to stopped state, which
-        // would prevent any consecutive calls to run()
-        // or poll() to do nothing. reset() could also revoke to the
-        // previous state but this might introduce some overhead of
-        // deletion and creation of threads and more.
-
+        StateMachineAsio<T>(out, "LID_CONTROL"), fLid(*this, *this)
+    {
         // State names
         T::AddStateName(Lid::State::kDisconnected, "NoConnection",