summaryrefslogtreecommitdiffstats
path: root/src/watch.hpp
diff options
context:
space:
mode:
authorRatan Gupta <ratagupt@in.ibm.com>2018-02-21 19:03:13 +0530
committerRatan Gupta <ratagupt@in.ibm.com>2018-02-22 21:05:19 +0530
commita45e086dc57f51efb882bf864e78fe678238deea (patch)
tree47099446e3b5f83528435a46af0efc90dd395d2a /src/watch.hpp
parent882d741c2392e2c37c2fbdaf1207e64ea6dc91a7 (diff)
downloadphosphor-dbus-monitor-a45e086dc57f51efb882bf864e78fe678238deea.tar.gz
phosphor-dbus-monitor-a45e086dc57f51efb882bf864e78fe678238deea.zip
Add callback contexts
Add the notion of a callback context. This enables callbacks to have logic around the conditions they were invoked in. There are two context on which call back can be invoked 1) Startup: during startup all the call backs will be called 2) Signal: As part of condition match on the watched properties. Callback would behave differently based on the context. eg: eventCallback 1) Startup: Don't take any action. 2) Signal: Create the Dbus Object for the event. Change-Id: If455558798ac3e44bbd8a93de0ce1b09d2e308ae Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
Diffstat (limited to 'src/watch.hpp')
-rw-r--r--src/watch.hpp4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/watch.hpp b/src/watch.hpp
index e36af9c..d420458 100644
--- a/src/watch.hpp
+++ b/src/watch.hpp
@@ -1,5 +1,7 @@
#pragma once
+#include "data_types.hpp"
+
namespace phosphor
{
namespace dbus
@@ -34,7 +36,7 @@ class Watch
virtual void start() = 0;
/** @brief Invoke the callback associated with the watch. */
- virtual void callback() = 0;
+ virtual void callback(Context ctx) = 0;
};
OpenPOWER on IntegriCloud