- From: Allan Thomson (althomso) <althomso@cisco.com>
- Date: Wed, 1 Apr 2009 09:30:09 -0700
- To: "Andrei Popescu" <andreip@google.com>
- Cc: Angel Machín <angel.machin@gmail.com>, "public-geolocation" <public-geolocation@w3.org>
Andrei - In what circumstance does an application decide to set this attribute to one value vs another? Is it based on environment? Is it based on time of day? Or other? Say I have a browser application that runs and wants to get location of the device so that it can show the user on a map. What input to the application causes the browser to set this attribute when calling the API? I understand the need for good power management and not having an API that causes poor power consumption on handheld devices. That makes sense. I still don't see how this attribute can be set intelligently by applications and until I understand that, I don't get why this attribute is so important in a standard location API. Allan -----Original Message----- From: Andrei Popescu [mailto:andreip@google.com] Sent: Wednesday, April 01, 2009 9:18 AM To: Allan Thomson (althomso) Cc: Angel Machín; public-geolocation Subject: Re: renaming enableHighAccuracy 2009/4/1 Allan Thomson (althomso) <althomso@cisco.com>: > > For me, a user (or the applications they use) will have no way of knowing whether GPS vs Wifi vs 3G is more or less power on their device. > I agree and this is exactly why we don't have a "useGps/useWifi/use3G" setting. We have a simple flag that expresses the app's requirement (low power, please) and the implementation makes the decision. Andrei
Received on Wednesday, 1 April 2009 16:30:50 UTC