[whatwg] ServiceWorker bottle-neck design flaw - MS Edge to the rescue?
maherrj at googlemail.com
Thu Mar 1 19:22:51 PST 2018
As you may be aware, I have been lobbying strongly here
and especially over there <https://github.com/w3c/ServiceWorker/issues/745> for
the introduction of a background geolocation capability with Web Apps.
So frustrated had I become that I spent the time to develop and document a
POC example with everything UA developers and Web App developers need to do
to implement background geolocation - documented sscce here
<https://drive.google.com/open?id=0B7Rmd3Rn8_hDNW1zSWRoXzBTclU> and, to
date, no one can tell me there’s anything wrong with it.
In this technical feed-back vacuum my mind began to ponder why, and then
drifted to “Cui Bono?”, and ultimately to conspiracy theories. For example:
- Phonegap/Cordova developers bribing W3C to sandbag BackgroundGeolocation
But only today did it dawn on me like a bolt of lightning to the brain!
There is a fundamental design flaw with the current ServiceWorker
design/implementations in that there is only ONE per UA. Jake Archibald et
al have been so blinkered with offline-first, cache, and the browser being
a proxy-server that they will not tolerate anything else monopolizing the
SW thread to the detriment of their fetch performance stats.
But God Bless Edge, notwithstanding their tardy arrival on the scene, who I
believe have specialist SW instances for PUSH, FETCH, A.N.Other. This is
Just add another specialist instance “GeoLocation” and we’re away.
Please don’t let self-interest stand in the way of this essential
functionality. Let’s go!
But my question here is this: - Can someone please confirm that Edge
implements multiple, specialist SW instances?
Cheers Richard Maher
More information about the whatwg