- From: Andrei Popescu <andreip@google.com>
- Date: Thu, 30 Oct 2008 20:58:33 +0000
- To: "Doug Turner" <doug.turner@gmail.com>
- Cc: "Chris Butler" <cbutler@dash.net>, "Greg Bolsinga" <bolsinga@apple.com>, olli@pettay.fi, public-geolocation@w3.org
On Thu, Oct 30, 2008 at 6:16 AM, Doug Turner <doug.turner@gmail.com> wrote: > > On Oct 29, 2008, at 8:21 PM, Andrei Popescu wrote: > >> On Wed, Oct 29, 2008 at 4:14 PM, Doug Turner <doug.turner@gmail.com> >> wrote: >>> >>> Looking at the defs., i do not see much of a difference between >>> PROVIDER_ERROR and NOT_FOUND (NOT_FOUND is just a special case of >>> PROVIDER_ERROR). >> >> Hmm, I think the difference between the two is more significant in the >> case of of a network-based provider: PROVIDER_ERROR would mean that >> the provider is not functioning correctly (the server is down, the >> client can't reach the network, etc), while NOT_FOUND would mean that >> everything is working fine, it's just that the server doesn't have >> enough data to tell where the client is. But I agree that maybe this >> is still not enough to warrant two separate error codes. >> >> Andrei > > > That is what the message attribute is for, right? From a web developer's > point of view PROVIDER_ERROR (something bad happened in the "thing" that > provides the geolocation position in the browser) and NOT_FOUND (the > position couldn't be determined) are the same. > Ok. So we have: UNKNOWN_ERROR = 1 (could be 0, but other error interfaces start at 1, e.g. http://www.w3.org/html/wg/html5/#mediaerror) PERMISSION_DENIED = 2 POSITION_UNAVAILABLE = 3 TIMEOUT = 4 Is that ok with everyone? Andrei
Received on Thursday, 30 October 2008 20:59:13 UTC