Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the
associated event trigger is chosen, what's generated to retrieve the
dbus data is specific to that trigger event. For signals, the data is
read from the given signal message. A method call is method specific and
is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
diff --git a/control/triggers.hpp b/control/triggers.hpp
index 35c3091..d170d0b 100644
--- a/control/triggers.hpp
+++ b/control/triggers.hpp
@@ -34,7 +34,7 @@
* @return Trigger lambda function
* A Trigger function that subscribes to a signal
*/
-Trigger signal(const std::string& match, Handler&& handler);
+Trigger signal(const std::string& match, SignalHandler&& handler);
/**
* @brief A trigger for actions to run at event init
@@ -47,7 +47,7 @@
* @return Trigger lambda function
* A Trigger function that runs actions at event init
*/
-Trigger init(Handler&& handler = nullptr);
+Trigger init(MethodHandler&& handler = nullptr);
} // namespace trigger
} // namespace control