Re: Drop lastPosition from Geolocation? from Doug Turner on 2008-11-19 (public-geolocation@w3.org from November 2008)

From: Doug Turner <doug.turner@gmail.com>
Date: Wed, 19 Nov 2008 11:18:15 -0800
To: "Thomson, Martin" <Martin.Thomson@andrew.com>
Cc: "Greg Bolsinga" <bolsinga@apple.com>, "Andrei Popescu" <andreip@google.com>, "Aaron Boodman" <aa@google.com>, "public-geolocation" <public-geolocation@w3.org>, "Richard Barnes" <rbarnes@bbn.com>
Message-Id: <A953BECD-412A-496F-8765-FED5E7DCE875@gmail.com>

>
> Note that with my proposal, you can still achieve the availability  
> goal.  Instead of including a position in the error callback, you  
> include an indication that cached data is available, but it was not  
> “fresh” enough.

Are you suggesting that instead of returning position unavailable, we  
add a new error code that expresses the fact that we might have a  
position available but it is outside of the "freshness" that you wanted?

Received on Wednesday, 19 November 2008 19:25:11 UTC