W3C home > Mailing lists > Public > public-geolocation@w3.org > October 2008

Re: PositionError Requests

From: Doug Turner <doug.turner@gmail.com>
Date: Wed, 29 Oct 2008 23:16:57 -0700
Cc: "Chris Butler" <cbutler@dash.net>, "Greg Bolsinga" <bolsinga@apple.com>, olli@pettay.fi, public-geolocation@w3.org
Message-Id: <7DB692EE-06E9-42E5-A3A2-96D03C1274AC@gmail.com>
To: "Andrei Popescu" <andreip@google.com>


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.

Doug
Received on Thursday, 30 October 2008 06:17:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:52 UTC