[Dev] Understanding Cynara scope.

Zhang, Xu U xu.u.zhang at intel.com
Mon May 19 09:24:02 GMT 2014

> -----Original Message-----
> From: Patrick Ohly [mailto:patrick.ohly at intel.com]
> Sent: Monday, May 19, 2014 3:33 PM
> To: Zhang, Xu U
> Cc: Lukasz Wojciechowski; Kis, Zoltan; José Bollo; dev at lists.tizen.org
> Subject: Re: [Dev] Understanding Cynara scope.
> On Mon, 2014-05-19 at 07:09 +0000, Zhang, Xu U wrote:
> > > So summing up:
> > > Cynara will be responsible for launching popups if needed.
> > [Zhang Xu ] The popups should be happed on application's installation.
> > Web and native app should parser the manifest firstly, and pass the
> > permissions to Cynara library to pop up dialog, right?
> When Cynara asks is entirely up to Cynara. It is *not* limited to installation
> time, at least not conceptually. There is an explicit parameter in the API for
> services which is meant to allow granting access temporarily (see the "Cynara
> session ID" mail thread), which implies popping up a dialog at runtime when
> that access needs to be granted the first time or be renewed.
[Zhang Xu ] Yes, it is not limited to installation, renew and update. When executing an web API, it may pop up a dialog to require user's confirmation.
There are three types of prompt for each API is determined by the policy: blanket, session and one-shot. For one-shot permission, web runtime must wait response from Cynary to go on other operations.
> --
> 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.

More information about the Dev mailing list