- From: Doug Turner <doug.turner@gmail.com>
- Date: Tue, 18 Nov 2008 10:46:40 -0800
- To: Aaron Boodman <aa@google.com>
- Cc: public-geolocation <public-geolocation@w3.org>, Greg Bolsinga <bolsinga@apple.com>, Richard Barnes <rbarnes@bbn.com>, Martin Thomson <Martin.Thomson@andrew.com>
On Nov 18, 2008, at 10:36 AM, Aaron Boodman wrote: > On Tue, Nov 18, 2008 at 9:57 AM, Doug Turner <doug.turner@gmail.com> > wrote: >> I think just using getCurrentPosition, with the modifiedSince >> option, is >> going to make you js code a bunch simpler -- you will only have one >> code >> path. > > First of all, we don't need 'modifiedSince', right? We already have > the timestamp property on the Position interface. > > The way I interpret what you are suggesting is that we get rid of > lastKnownPosition and leave it up to the UA to cache positions across > applications as it sees fit. In that world, I would see vendors > caching very conservatively (on the order of a few seconds). Hmm. Youre proposing that we ignore the option all together, and just have GetCurrentPosition/WatchPosition return whatever cached value it may have -- Leaving it up to the UA's to determine their own caching policy? Right?
Received on Tuesday, 18 November 2008 18:47:17 UTC