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

Re: skeleton Geolocation API

From: Aaron Boodman <aa@google.com>
Date: Thu, 24 Jul 2008 13:59:23 -0700
Message-ID: <278fd46c0807241359t7457c53enae104d3bb33ee1c7@mail.gmail.com>
To: "Alec Berntson" <alecb@windows.microsoft.com>
Cc: "Andrei Popescu" <andreip@google.com>, "Shyam Habarakada" <shyamh@microsoft.com>, "Chris Prince" <cprince@google.com>, "Doug Turner" <doug.turner@gmail.com>, "public-geolocation@w3c.org" <public-geolocation@w3c.org>

On Thu, Jul 24, 2008 at 1:56 PM, Alec Berntson
<alecb@windows.microsoft.com> wrote:
> What about the case where the user has an external GPS puck that they can plug-in or unplug? In that case the availability of the API is transient. I don't think having the geolocation object become null is a good solution. An error regarding "NotAvailable" seems like a cleaner method.

I'm not sure. To give context, what are some devices where this won't
be supported at all? I think at least with Gears, we can always fall
back to IP-based geolocation.

- a
Received on Thursday, 24 July 2008 21:00:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 March 2012 18:13:39 GMT