5 ms·
ServiceWorkers and Firefox
- technological 12y agoAre web workers,any way related to service workers ??
- wereHamster 12y agoRead this overview: http://jakearchibald.com/2014/service-worker-first-draft/ http://jakearchibald.com/2014/service-worker-first-draft/
- walterbell 12y ago> It's like having a proxy server running on the client Is that "proxy server" under the control of the client or the origin site? e.g. can it perform content transformation? That post talks mostly about offline caching, are there other use cases driving the proposal?
- rictic 12y agoIt's under the control of the origin site (for client manipulation there are stable extension apis in most browsers for this already). The primary use case is caching and offline / partial connectivity, but it's full javascript and the service worker can construct arbitrary responses. Here's a good overview: https://www.youtube.com/watch?v=4uQMl7mFB6g https://www.youtube.com/watch?v=4uQMl7mFB6g
- aikah 12y agoSo it's basically an https proxy server running on the client in a worker thread that can work offline right?
- SimeVidas 12y agoSounds about right :)
- derefr 12y agoSo, like the HTML5 Application Cache, but actually useful.
- deleted 12y ago[deleted]
- dccoolgai 12y agoThis is exciting. I don't track too many of these standards efforts closely, but I've been following this one for a while. I honestly think that offline-first will do more to close the gap with native than anything.
- th3iedkid 12y agoIs there any work on having something like HTML5 lite with a lighter browser implementation?Because things like these call for more devices(sockets) to used , which takes more resourceful computers to accomplish.Is there any work on actually reducing the browser foot-print , right from spec level?