Use dbus signal for sending expired noti to client 84/45284/1 accepted/tizen/mobile/20150812.110325 accepted/tizen/tv/20150812.110339 accepted/tizen/wearable/20150812.110352 submit/tizen/20150812.024336
authorSangyoon Jang <s89.jang@samsung.com>
Tue, 4 Aug 2015 10:23:43 +0000 (19:23 +0900)
committerSangyoon Jang <s89.jang@samsung.com>
Tue, 4 Aug 2015 10:44:56 +0000 (19:44 +0900)
commit51b432e318eba952ad7f0fd19ea2bb078eeee189
tree77f83ec0336980234c6d415f2f2fef5eccec0832
parent60782eee2d2745e4f623feaf0c2f5652837c058e
Use dbus signal for sending expired noti to client

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>
alarm-manager.c
alarm_mgr.xml
include/alarm-internal.h
src/alarm-lib.c