- From: Andrei Popescu <andreip@google.com>
- Date: Wed, 6 May 2009 16:00:15 +0100
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Max Froumentin <maxfro@opera.com>, public-geolocation@w3.org
On Wed, May 6, 2009 at 3:51 PM, Anne van Kesteren <annevk@opera.com> wrote: > On Wed, 06 May 2009 14:52:02 +0200, Max Froumentin <maxfro@opera.com> wrote: >> With an abort mechanism the callback would never be called after you've >> cancelled, whereas with the solution you suggest it could happen a while >> later, and could possibly interfere with subsequent calls to >> getCurrentPosition. And also, interrupting the GPS would save CPU cycles >> that would be wasted otherwise > > It seems that if the concern is wasting CPU cycles it should be up to the user and user agent (and probably the OS) to safe them rather than the page author otherwise we end up with the situation where some pages allow this and others do not. > I don't think CPU was the concern at all. Rather, the concern was to save power and to provide some small convenience to developers. Andrei
Received on Wednesday, 6 May 2009 15:00:53 UTC