- From: Greg Bolsinga <bolsinga@apple.com>
- Date: Mon, 16 Mar 2009 18:11:41 -0700
- To: public-geolocation <public-geolocation@w3.org>
These are all implementation details, and I don't think they should be in the spec. As an alternate to arguing they be removed, can timeout & maximumAge be optional suggestions? enableHighAccuracy is already defined as a hint. Some UAs may not have a way to determine the age of a location, for example. Here's how you'd do remove them, have a simpler API, and still be able to get all of the above. Drop getCurrentPosition from the API completely. Have watchPosition only. As watchPosition returns locations to your callback, you watch the accuracy for a value you are interested in (this gets around the hint part of enableHighAccuracy). If you don't care, you take the first callback and clearWatch (this is getCurrentPosition path). If you don't get an accurate enough one in time (via your own JavaScript timer) you clearWatch (this is the timeout path). This also allows the developer to define accuracy with their own standards (with 100 meters, etc), as "enableHighAccuracy" is only a hint. Thanks, -- Greg
Received on Tuesday, 17 March 2009 01:12:22 UTC