Re: [geofencing-api] Why is geofencing design tied to service workers?

@allanjuma where do you put the check for opening hours on your 
restaurant/shop? (Umbrella specials in the rain perhaps?)

a) In the User-Agent as part of the GeoFence API options list
b) No that's silly, just check in the Service Worker

My guess is you'll opt for (b) and everyone else will just opt for 
whatever they do with Java geofences at the moment. (After all copying
 what is already there is considered a no-brainer by those who don't 
like to think.)

I say to you that the entrie raison d'etre for geofencing is that it's
 supposed to save battery life by enforcing/implementing the fence in 
the UA and not needing to spin up a SW. Therefore it should check 
hours in the API to the UA yes? But opening hours aren't engraved in 
stone. How do I tell the UA I want to vary them or vary the radius of 
the geofence for that matter?

> my2ยข starting out with a bare minimum implementation of just 
geofencing might help get more interest and feedback while limiting 
risk.

But why can't you see that what you're asking for is a concoction and 
no where near a "bare minimum"???

GeoLocation ***IS*** the bear minimum! GeoFencing is just one 
implemented application of geolocation. You Sir, have deliberately 
sought to cut off developers legs by limiting them to a myopic world 
of geofence rigidity that is next to useless :-(

BTW Here is another recent Use Case (with geofence implementing code 
(circle and rectangle)) that you may find interesting: -
https://bugs.chromium.org/p/chromium/issues/detail?id=383125#c38 Start
 reading from comment #38

(And no, there was no TPAC in Bora Bora this year. You did not miss 
out.)

-- 
GitHub Notification of comment by RichardMaher
Please view or discuss this issue at 
https://github.com/w3c/geofencing-api/issues/25#issuecomment-201085672
 using your GitHub account

Received on Friday, 25 March 2016 00:37:31 UTC