On Tue, 2014-06-17 at 08:59 +0000, Zhang, Xu U wrote: > The general flow for Tizen API case is as below: > (1) When Tizen device JS API such as Bluetooth.read() is called, render > process will send IPC to extension process firstly. > (2) When extension process receives the message, extension process will call > SAPI
... or some other system services. I suggest to describe the extension process as "calling the system" instead of "calling SAPI", because for the security architecture of Crosswalk it is irrelevant how the system exposes services, as long as it does securely. It is relevant for actually writing the extension code, of course. Right now, extensions cannot call SAPI (does not exist yet) while they can call existing services. This takes us from architecture considerations into the realm of the more practical "how do we actually get work done"; not sure whether we want to go there. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
