Le 02/12/2014 09:59, Kis, Zoltan a écrit :
Nothing prevents anyone from deploying a platform service which can
communicate both with native apps and native web extensions using the
same IPC, and then deploy either a native or web front-ent. This
should be the case of regulatory HW-specific API's such as telephony,
cellular messaging, Bluetooth, NFC, etc.
Yes, if your Apps are not delivered in the same packages, the security
system will NOT let them share anything.
For those apps which would like to deploy a generic "service run as an
app", without being part of the platform, they need a native IPC layer
to communicate with graphical front-ends (and the permissions needed
to use the underlying API's). This communication mechanism can be
app-private, or public platform-wide IPC, but one thing is sure: it
does not belong to the web runtime. In that sense Crosswalk does
support this model, since it provides al mechanisms to deploy native
extensions together with web apps. Existing web permissions should
cover it, but if we speak about a new platform wide IPC designed for
this, then we could add a special permission to it. Of course, the
platform security model needs to support it to start with.
Sorry, only Platform Apps and Services can deliver what you propose. An
App is far more constrained.
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
