On Wed, Jul 2, 2014 at 3:18 PM, José Bollo <[email protected]> wrote: > On mer, 2014-07-02 at 09:08 +0200, Patrick Ohly wrote: > > (snip) > > >> The capi for email doesn't allow fetching, the email-service does. So we >> need to clarify first which one is supposed to be wrapped. >> > > I raised the same conclusion after studying the implementation of WRT in > tizen 2. Here is the place where I put elements of this study: > > https://wiki.tizen.org/wiki/Security/Privileges_Study_For_Tizen3#Reconstruction_of_dependencies_of_modules_of_wrt-plugins-tizen > > As you can see there, the "Messaging" module uses the services of > platform/core/messaging/email-service and of > platform/core/messaging/msg-service. None of it are part of the core > API. > > These services are (from the client side) accessing a server through > sockets/IPC. No DBUS.
This is not valid for Tizen IVI, only for mobile. In IVI, - Messaging and Email domain uses MAP Bluetooth profile to access messaging data. Through DBUS. - the telephony domain uses oFono DBUS API's and HFP+PBAP Bluetooth profiles. - the contacts domain uses PBAP Bluetooth profile to access data, through DBUS. They are NOT using the dependencies listed in the wiki pages. Please update everywhere, unless you want to build a SAPI on false assumptions. Best regards, Zoltan _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
