W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: solving the CPU usage issue for non-visible pages

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 20 Oct 2009 17:36:55 -0700
Message-ID: <63df84f0910201736w371da996n39b3811827a0d192@mail.gmail.com>
To: robert@ocallahan.org
Cc: "Ennals, Robert" <robert.ennals@intel.com>, "public-webapps@w3.org" <public-webapps@w3.org>
On Tue, Oct 20, 2009 at 4:44 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
> On Wed, Oct 21, 2009 at 11:59 AM, Ennals, Robert <robert.ennals@intel.com>
> wrote:
>>
>> Should we also consider the case where a web site wants to keep its
>> interface up to date with some server state and is using up CPU time and
>> network resource to do so?
>
> You could abuse my proposal to do this, by periodically (as frequently as
> you run script now) calling requestAnimationFrame and seeing if you actually
> get a paint event. Maybe that's not an ideal solution, though.

Yeah, I think having an API that lets you check if the page is
visible, as well as an event that lets you know when the visibility
changes, would be a good idea. That's better than adding *WhenVisible
APIs, like setTimeoutWhenVisible, EventSourceWhenVisible, etc.

/ Jonas
Received on Wednesday, 21 October 2009 00:37:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:34 GMT