Hi List and Tizen team, I'm reviewing to Tizen source codes under framework dir. Especially middleware and their client libraries. Below list is what I've reviewed about IPC in each middleware.
* D-Bus - framework/appfw/slp-pkgmgr : D-Bus - framework/appfw/alarm-manager : D-Bus - framework/connectivity/connman : D-Bus - framework/connectivity/bluez : D-Bus * Custom IPCs using unix or inet socket - framework/system/system-server : libslp-sysman and heynoti - framework/system/power-manager : libslp-pm - framework/system/sensor-framework : libslp-sensor - framework/appfw/aul-1 : libaul_mods - framework/connectivity/nfc-manager : libnfc - framework/pim/contacts-service : libcontacts-service - framework/security/drm-client : libdrm-client - framework/security/secure-storage : libss-client - framework/security/security-server : libsecurity-server-client * Custom IPCs using inotify - framework/appfw/heynoti : libheynoti - framework/appfw/vconf : libvconf - framework/pim/calendar-service : libcalendar-service I've thought that D-Bus is *official* and *preferred* IPC for Tizen. Most of OSS modules such like ConnMan or GeoClue in Tizen use D-Bus as IPC. But most of middleware from SLP have their own custom IPC and implement them in each client libraries. In other word, Tizen framework uses at least 15 different IPC. I want to believe those custom IPCs are reliable, stable and powerful. However I think that it looks not good in point of architecture design. What is a *Official* IPC in Tizen ? If it should be D-Bus, Is there any plan to change custom IPCs of slp modules to D-Bus? Best Regards, JC _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
