Re: Drop lastPosition from Geolocation?

fwiw I think the point of this was so that you didn't ahve to wait  
until the callback happened.... so if one web application was using  
geolocaiton, another application could get a quick sync result when it  
first starts up.


On Nov 17, 2008, at 2:25 PM, Greg Bolsinga wrote:

> +1 Yeah, as far is I can tell, it isn't set unless you have set up a  
> watch or get in the first place. Might as well cache it yourself, if  
> you need it for some reason.
>
>
> On Nov 17, 2008, at 2:18 PM, Thomson, Martin wrote:
>
>> +1
>>
>> Caching is better left to the "location provider".  But I suspect  
>> that I have a different perspective and reasoning.
>>
>> Add:
>> 3) The only benefit this adds is for the browser/user/device.   
>> There is no incentive for the site to use this, so it will  
>> inevitably will be ignored by sites.
>>
>> There are better ways to achieve the goals this is trying to  
>> address.  You've already heard from me on that.
>>
>> Martin
>>
>>> -----Original Message-----
>>> From: public-geolocation-request@w3.org [mailto:public-geolocation-
>>> request@w3.org] On Behalf Of Doug Turner
>>> Sent: Monday, 17 November 2008 3:42 PM
>>> To: public-geolocation
>>> Subject: Drop lastPosition from Geolocation?
>>>
>>>
>>> Where are we on the lastPosition attribute?
>>>
>>> I would like to remove it because:
>>>
>>> 1) synchronous API are impossible to deal with from a UI/Security  
>>> POV.
>>>
>>> 2) do not see the performance win they are supposedly have.
>>>