Remove vconf ipc based logic for syncronizing with master 19/10119/2 accepted/tizen/ivi/genivi accepted/tizen/ivi/release tizen_ivi_genivi tizen_ivi_release accepted/tizen/20130918.235338 accepted/tizen/20130918.235403 accepted/tizen/20130918.235413 accepted/tizen/20130920.205126 accepted/tizen/ivi/genivi/20140131.061721 accepted/tizen_ivi_release/20131120.050538 ivi_oct_m2 submit/tizen/20130918.233920 submit/tizen_ivi_genivi/20140131.060719 submit/tizen_ivi_release/20131120.021413 submit/tizen_ivi_release/20131120.025937
authorRusty Lynch <rusty.lynch@intel.com>
Tue, 10 Sep 2013 16:26:55 +0000 (09:26 -0700)
committerRusty Lynch <rusty.lynch@intel.com>
Wed, 18 Sep 2013 23:32:53 +0000 (16:32 -0700)
commit22075fff68729c4decd90672091c3c4075982435
tree94134bba3456f2c4284345b95b08044beabd2659
parente8870a00bc1273a32bdf6c63dfa84e8c4b251a4c
Remove vconf ipc based logic for syncronizing with master

We now have systemd auto activation support for whatever process
provides the notification socket.  As a result we can now greatly
simplify the client logic that was attempting to provide the same
capability as socket activation in that the client was able to
register with the server before the server was actually started.

Change-Id: I93a8af60cfba30f775cfa0af90c8c267c9678819
Signed-off-by: Rusty Lynch <rusty.lynch@intel.com>
CMakeLists.txt
include/notification_ipc.h
packaging/notification.changes
packaging/notification.spec
src/notification.c
src/notification_ipc.c