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.
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. Note that these apps (mostly games) tend to have a memory footprint comparable to a web app, and it depends on case by case whether the resource gain is significant enough for the additional trouble and extra IPC hop, which may undermine the benefits. Also, check how many things run smoothly in a browser (especially games) that 3 years ago we didn't think they would. However, once I expect developers reserve the right to know better, I agree we should document the mechanism how to achieve this in Tizen. But again, I don't see this as a web runtime specific mechanism, just as a best-known-method description using existing runtime mechanisms. Regards, Zoltan On Tue, Dec 2, 2014 at 3:55 AM, Bumjin Im <[email protected]> wrote: > Since I'm not a web guy so not sure about it but as far as I know Service > Workers are not fulfilling the requirements of hybrid app. > There are mainly 2 reasons why Tizen 2.x supports are 1st, for service app > and UI app that service app runs in a background always even though the UI > app is not running, 2nd, to support *something* the web API doesn't support > yet. > I think running huge web apps for background listening will consumes too much > memory for mobile devices especially smart watches. > > Bumjin > > ------- Original Message ------- > Sender : Kis, Zoltan<[email protected]> > Date : 2014-12-01 21:24 (GMT+09:00) > Title : Re: [Dev] Question about Crosswalk and hybrid apps > > On Mon, Dec 1, 2014 at 7:02 AM, Bumjin Im wrote: >> I'm not sure but hybrid app is not only for speeding, but also for some >> service style apps (such as messanger) that need to support continuous >> operation. As far as I know many app developers demand such feature. >> In fact, I don't know Crosswalk extension can support those "service" apps. > > Service workers are meant to solve that use case in browsers and > runtimes. So one can develop a web message app or a web dialer, since > it will be able to run a service worker in the background and wake up > the front-end app when needed. > http://www.w3.org/TR/2014/WD-service-workers-20141118/ > > Best regards, > Zoltan _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
