Re: [w3c/ServiceWorker] Expose GeoLocation to workers (#745)

Addendum: -

Another really useful resource/battery friendly aspect of the above design is that regardless of how many geolocation-using web-apps are "active" on the phone (while it's in a pocket etc) there is only **one** daemon (be it a UA or Google Play) that is consuming the listen overhead and deciding what's interesting.

Also, had a look at postMessage() and its event and can't see any collapse potential. I'm also guessing the only pipe or queue for messages is the Service Worker's event queue. So would it be ok to listen for a Focus() event on the App window or document and discern that all postMessage events would have been received before the focus event? Or if a focus event is first then it can setTimer(0,allGeoUpdatesReceived) ?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/745#issuecomment-304185250