W3C home > Mailing lists > Public > public-device-apis-log@w3.org > November 2017

Re: [sensors] Generic Sensor & Wake Lock API use cases

From: MeritBased via GitHub <sysbot+gh@w3.org>
Date: Mon, 13 Nov 2017 00:23:25 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-343781201-1510532604-sysbot+gh@w3.org>
@pozdnyakov can I please ask you 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!



-- 
GitHub Notification of comment by MeritBased
Please view or discuss this issue at https://github.com/w3c/sensors/issues/323#issuecomment-343781201 using your GitHub account
Received on Monday, 13 November 2017 00:23:28 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 November 2017 00:23:28 UTC