- From: MeritBased <notifications@github.com>
- Date: Tue, 14 Nov 2017 02:41:11 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 14 November 2017 02:41:36 UTC
Can I please ask you all to consider looking outside the W3C/IETF opinion pool for solution and design ideas on this? Stackoverflow for example: - [Background Geolocation ServiceWorker - onMessage Event order when Web App regains focus](https://stackoverflow.com/questions/44233409/background-geolocation-serviceworker-onmessage-event-order-when-web-app-regain) has over 430 views and 12 votes and the answer a further 2 votes. [Expected ratio of ServiceWorker instances to Geolocation Updates](https://stackoverflow.com/questions/45206149/expected-ratio-of-serviceworker-instances-to-geolocation-updates) has 126 views plus 5 and 1 votes respectively. The source-code for the TravelManager POC and polyfill, along with an aaa_readme.txt, can be found [here](https://drive.google.com/drive/folders/0B7Rmd3Rn8_hDNW1zSWRoXzBTclU) If you wish to see the example without copying then, after reading the readme file, run the Ultimate Web App from [Brotkrumen](https://hypocampus.applications.uwa.edu.au/travelmanager.html) The CPU Wake Lock may well be all that is needed for other/true sensors but Background Geolocation needs the Service Worker Travel Manager! -- 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-344128148
Received on Tuesday, 14 November 2017 02:41:36 UTC