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

Re: skeleton Geolocation API - Error codes

From: Doug Turner <doug.turner@gmail.com>
Date: Mon, 4 Aug 2008 11:20:41 -0700
Cc: Andrei Popescu <andreip@google.com>, Chris Butler <cbutler@dash.net>, Alec Berntson <alecb@windows.microsoft.com>, Chris Prince <cprince@google.com>, Aaron Boodman <aa@google.com>, "public-geolocation@w3c.org" <public-geolocation@w3c.org>
Message-Id: <6F33FB96-EC51-4B8A-AA29-99DCC5F2BDB3@gmail.com>
To: Shyam Habarakada <shyamh@microsoft.com> 


On Aug 4, 2008, at 11:07 AM, Shyam Habarakada wrote:

>> -----Original Message-----
>> From: Doug Turner [mailto:doug.turner@gmail.com]
>>
>> I disagree that we need  to or should expose http protocol specific
>> error codes.  Otherwise sounds fine.
>
> Hi Doug,
> Would you mind sharing with us your reasoning here? That would give  
> us more context. Thanks


I see no need to special case one class of geolocation providers by  
exposing its specific errors codes.  We should hide these  
implementation details behind general error codes, or by providing a  
separate optional interface or set of attributes.

Doug
Received on Monday, 4 August 2008 18:21:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 August 2009 20:54:07 GMT