On gio, 2014-09-04 at 07:07 +0000, Zhang, Xu U wrote: > There are two point for Crosswalk to call Cynara related APIs.
No I'm thinking that there are 3 points, the third being the launching process > 1. Crosswalk installer registers application's permission list to Cynara. > I think installer will not call Cynara admin APIs directly but call security > manager APIs. > Right? Yes I think so. > 2. Crosswalk browser process checks application privilege by calling Cynara > client APIs during runtime. Yes I think so. About the launcher, it should be privileged and rely on security-manager to set the security context before becoming tizen-extension-process. That is my humble understanding. Best regards josé > > Best Regards > Zhang Xu > > -----Original Message----- > > From: José Bollo [mailto:[email protected]] > > Sent: Thursday, September 4, 2014 2:42 PM > > To: Zhang, Xu U > > Cc: Whiteman, John L; Oda, Terri; Lukasz Wojciechowski; [email protected] > > Subject: Re: [Dev] [Cynara] Async admin API proposal > > > > On gio, 2014-09-04 at 01:59 +0000, Zhang, Xu U wrote: > > > I am sorry that I have made a mistake on web API running process. It > > > is should be: > > > > > > One is Tizen device APIs, which will run the extension process. The > > > other is some W3C web APIs, which including Geolocation, media and so > > > on will run in the browser process. > > > > Hi, > > > > cool, it confirms our understanding. > > > > But in my understanding, the web process does not require admin accesses to > > cynara, only client access. > > > > What am I missing? > > > > Best regards > > José > > > > > _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
