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

Re: Drop lastPosition from Geolocation?

From: Doug Turner <doug.turner@gmail.com>
Date: Wed, 19 Nov 2008 09:52:19 -0800
Cc: Greg Bolsinga <bolsinga@apple.com>, Aaron Boodman <aa@google.com>, public-geolocation <public-geolocation@w3.org>, Richard Barnes <rbarnes@bbn.com>, Martin Thomson <Martin.Thomson@andrew.com>
Message-Id: <E1DE243D-1790-4028-9691-D83571DFCA74@gmail.com>
To: Andrei Popescu <andreip@google.com>


On Nov 19, 2008, at 9:43 AM, Andrei Popescu wrote:

> Hi Doug,
>
> I like the modifiedSince option, but I do have a question. Right now,
> lastPosition allows you to quickly fallback to some default action if
> lastPositon is null or too old.
>
> In the async solution, the only way to achieve the same thing is by
> both specifying modifiedSince and setting timeout to 0, right? This
> would force the UA to immediately invoke the errorCallback (with error
> TIMEOUT or POSITION_UNAVAILABLE?) in case it does not have a fresh
> enough cached position. What happens if the page does not have
> permission? I think the errorCallback should be immediately invoked
> with error PERMISSION_ERR, right?


Right, if the document isn't given permission to use  
navigator.geolocation, then the errorCallback, if set, will be called  
with the PERMISSION_DENIED error code.
Received on Wednesday, 19 November 2008 17:52:59 GMT

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