diff options
| author | Sangyoon Jang <s89.jang@samsung.com> | 2015-08-04 19:23:43 +0900 |
|---|---|---|
| committer | Sangyoon Jang <s89.jang@samsung.com> | 2015-08-04 19:44:56 +0900 |
| commit | 51b432e318eba952ad7f0fd19ea2bb078eeee189 (patch) | |
| tree | 77f83ec0336980234c6d415f2f2fef5eccec0832 /alarm_mgr.xml | |
| parent | 60782eee2d2745e4f623feaf0c2f5652837c058e (diff) | |
| download | alarm-manager-51b432e318eba952ad7f0fd19ea2bb078eeee189.tar.gz alarm-manager-51b432e318eba952ad7f0fd19ea2bb078eeee189.tar.bz2 alarm-manager-51b432e318eba952ad7f0fd19ea2bb078eeee189.zip | |
Use dbus signal for sending expired noti to clientsubmit/tizen/20150812.024336accepted/tizen/wearable/20150812.110352accepted/tizen/tv/20150812.110339accepted/tizen/mobile/20150812.110325
In current implementation, each client register own dbus object to
receive alarm expired signal from alarm-server.
When an alarm expired, alarm-server finds service name(app or daemon) and
calls directly using dbus method call.
But using dbus signal is more reasonable, alarm-server can just emit
dbus signal to notify alarm expired.
Furthermore, in Tizen 3.0, if a service who doesn't have busconfig
cannot own name and send method call on system bus.
Change-Id: Ic6a3ea44046cc963ca3fc1b94c2433ff64e3e33a
Signed-off-by: Sangyoon Jang <s89.jang@samsung.com>
Diffstat (limited to 'alarm_mgr.xml')
| -rw-r--r-- | alarm_mgr.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/alarm_mgr.xml b/alarm_mgr.xml index 4facb9d..faf03a0 100644 --- a/alarm_mgr.xml +++ b/alarm_mgr.xml @@ -139,5 +139,9 @@ <arg type="s" name="tzpath_str" direction="in" /> <arg type="i" name="return_code" direction="out" /> </method> + <signal name="alarm_expired"> + <arg type="i" name="alarm_id" /> + <arg type="s" name="app_service_name" /> + </signal> </interface> </node> |