Re: Drop lastPosition from Geolocation?

Greg, are you happy with the modifiedSince option?

Aaron, any further objection?

On Nov 19, 2008, at 9:30 AM, Greg Bolsinga wrote:

> On Nov 19, 2008, at 9:19 AM, Doug Turner wrote:
>> I was thinking it would be something like -- the web app could say,  
>> "I don't care if the location is a bit stale".  So, if a web app  
>> passed 600 as the modifiedSince, that would mean that the UA could  
>> return a position that is <= 10 minutes old.
>>> An alternative could be if the UA can't provide a position within  
>>> the PositionOptions timeout parameter, it will return the last  
>>> position obtained by the UA, across all pages? This would need a  
>>> flag supplied to let the developer know they are getting  
>>> potentially stale data. Perhaps this can be a Position field in  
>>> the PositionError that is lastPosition, only set when the error  
>>> code is TIMEOUT?
>> That is an idea.  I am not sure I like returning a position at all  
>> in most error cases.
> Yeah, should it be NULL except in the timeout case?
> Thinking about it more, in this scenario the user would have to wait  
> for the timeout to expire to get the stale data. That is probably  
> acceptable, because if the location is returned before that, they  
> don't get stale data. If they set timeout=0, they will get the stale  
> data, unless something else is already 'hot' and has the real  
> position.
> -- Greg

Received on Wednesday, 19 November 2008 17:33:38 UTC