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
Richard Maher commented
Good to see this and the Push API get up! Well done.
Thanks for prioritizing this for Edge. Does this mean it will also be implemented for the Universal Windows Platform?
Yay Go Microsoft Go!
Matthew Rath commented
This needs to be implemented as soon and as thoroughly as possible.
The single biggest problem i face as a developer of 8 years is how to make websites handle poor or even no connectivity.
Chrome and opera already have their own implementations and FF will be migrating from their nightly build soon enough -
Move your *** MS or get left behind.
For Hosted Web Apps (HWA) aka Westminster service workers will replace the depreciated AppCache and give developers far more granular control over what they cache and when.
If AppCache it to truly be depreciated, support for service workers needs to be added sooner rather than later.
Umberto Arreghini commented
Service worker is a fundamental feature for web apps development.
Wouter van Dam commented
We are looking to install several hundred machines in the upcoming months and expect to be installing another batch in the months after that. Currently an evaluation is going on to decide whether all these machines will be running Android or Windows 10 with Edge. Implementing this feature - preferably including background sync - would strengthen the case for the Windows solution.
Can i haz this now plz, k thks bye
Lewis Phạm commented
@Adeel The major difference between SharedWorker and ServiceWorker is lifetime. ServiceWorker is an event emitter with a temporary lifetime, while SharedWorker remains persistent until all pages are closed.
Nagaraju Epuri commented
Any update here?? This is next big thing after XHR. I strongly believe this is going to be a game changer for future web.
Matthias Götzke commented
We are leveraging this in an application used by on site 'technicians'. Usually they have 3 or 4g connectivity, but inside buildings they can become temporarily offline. Which is where service worker kicks in. This is the reason we use android devices not windows phones.
This will kill 80% of native apps.
The next big thing after XHR!
The best thing after XHR.
A must have for any serius web application developement.
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.