Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #30979

Web App Background Processing with Service Workers

Cross-posted to 3 groups.

Show all headers | View raw

The next couple of days will see a W3C Toronto F2F meeting on Service 
Workers: -
https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/16-07-28-29SW.md 


If you want to see Service Workers reach their full potential in 
enabling Background Processing for HTML5 Web Apps then please attend or 
lend your voice to: -

https://github.com/slightlyoff/ServiceWorker/issues/932

Below is the email I sent directly to the attendees from Mozilla, 
Microsoft, Apple, Google, and Samsung: -

As someone who is a huge fan of ServiceWorker technology and also 
desperate to see it move on from its offline-first requirement genesis 
and fulfill its rightful place as the home to all HTML5 WebApp 
BackGround processing, I beg you to please find time in Toronto to 
discuss the following: -

WebApp features requiring a Background listener capability are already 
queuing at the ServiceWorker door. For example: -

TravelManager - GeoLocation
HelloMyApp - SpeechRecognition for wake-up keyword
CalendarManager - Scheduled events
Sensor - AmbientLight, Temperature change etc
And so on . . .

Issues: -

1) How to handle interface discrepancies between ForeGround Javascript 
API and BackGround ServiceWorker interface. Make event signature the same?

2) Provide an option to suspend ServiceWorker instantiation if WebApp is 
in ForeGround/Visible

For a detailed description of how I see background GeoLocation aka 
TravelManager working, please see: - 
https://github.com/slightlyoff/ServiceWorker/issues/745#issuecomment-182624198

Cheers and Good-Luck,
Richard Maher (Simple code-cutter)

Back to comp.lang.javascript | Previous | Next | Find similar | Unroll thread

Thread

Web App Background Processing with Service Workers Richard Maher <maherrj@gmail.com> - 2016-07-27 14:32 +0800

csiph-web