W3C home > Mailing lists > Public > public-geolocation@w3.org > November 2008

Re: Drop lastPosition from Geolocation?

From: Aaron Boodman <aa@google.com>
Date: Tue, 18 Nov 2008 10:36:48 -0800
Message-ID: <278fd46c0811181036y7f130d4dn1ceacbbd9fe958a6@mail.gmail.com>
To: Doug Turner <doug.turner@gmail.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 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).

- a
Received on Tuesday, 18 November 2008 18:37:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 August 2009 20:54:08 GMT