ServiceWorkers (formerly Navigation Controllers) are a new system that provides event-driven scripts that run independent of web pages. They are similar to SharedWorkers except that their lifetime is different and they have access to domain-wide events such as network fetches.
Service Workers are now under active development in MS Edge. You can track progress at https://developer.microsoft.com/en-us/microsoft-edge/platform/status/serviceworker
W3C draft (http://www.w3.org/TR/service-workers/) states:
"This design borrows heavily from developer and vendor experience with Shared Workers .."
The current status of service worker in on modern.ie is under consideration: http://dev.modern.ie/platform/status/sharedwebworkers.
While that of shared worker is "Not currently planned".
Why are you guys stalling Shared Worker and considering ServiceWorker, when Service worker leverage the core functionality of Shared worker?
Hiroshi Kawada commented
Mobile web should support offline features. In my opinion, Web doesn't need to get native application scope, but mobile users want features that covers mobility use case and mobile application lifetime. Push notification helps better conversion, connectivity of users life and powerful engagement.
Henrik Valerian commented
Please support the service worker spec.
The most important new feature needed for web applications
Ege Özcan commented
Service Workers are *essential* for making reliable, high-performance offline applications. Unless we have a miracle happening in the connectivity world, enabling high-bandwidth data access for cheap anywhere in the world, lack of Service Workers is a show-stopper for various kind of offline apps. No, HTML appcache doesn't cover most cases.
Matheus Kautzmann commented
The Service Worker spec will empower the creation of new and better offline apps. Please support it.
Any updates here?
Šime Vidas commented
The title of this entry should be amended with “(mother effing OFFLINE web apps)” to make it absolutely clear what this is.