W3C home > Mailing lists > Public > public-geolocation@w3.org > April 2009

Re: renaming enableHighAccuracy

From: Andrei Popescu <andreip@google.com>
Date: Wed, 1 Apr 2009 13:29:28 +0100
Message-ID: <708552fb0904010529pb0f8693j1749b5b6f8e70de1@mail.gmail.com>
To: "Allan Thomson (althomso)" <althomso@cisco.com>
Cc: public-geolocation <public-geolocation@w3.org>
Hi Allen,

On Wed, Apr 1, 2009 at 12:16 AM, Allan Thomson (althomso)
<althomso@cisco.com> wrote:
> Andrei -
> I have a clarifying question.
> Is the intent of the attribute to force the client to ONLY use low power
> or is it intended to "prefer" low power over higher powered options?

It's probably simplest if we let 'lowPowerOnly' be a requirement. This
is for two reasons:

1. If a developer specifies it (note that 'lowPowerOnly' defaults to
false), it means power consumption is important to their app.
2. It makes the API behavior more consistent: if this requirement
cannot be satisfied, the errorCallback will be invoked and the app
will know about it. It could then try again without the 'lowPowerOnly'
flag set.

Of course, since we let the definition of high / low power up to the
implementation, we still cannot guarantee identical behavior across
all implementations. But we can provide guidelines (e..g don't power
up GPS if lowPowerOnly is set), as I mentioned earlier. Also, we
should probably add a new errror code LOW_POWER_PROVIDERS_UNAVAILABLE
(or similar) for the case in 2. above?

Received on Wednesday, 1 April 2009 12:30:13 UTC

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