- From: Thomson, Martin <Martin.Thomson@andrew.com>
- Date: Mon, 17 Nov 2008 16:18:18 -0600
- To: "Doug Turner" <doug.turner@gmail.com>, "public-geolocation" <public-geolocation@w3.org>
+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. > > Doug > ------------------------------------------------------------------------------------------------ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any unauthorized use of this email is prohibited. ------------------------------------------------------------------------------------------------ [mf2]
Received on Monday, 17 November 2008 22:19:01 UTC