W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2010

RE: CPU API (Re: [sysinfo] draft ready for review)

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Tue, 5 Jan 2010 16:03:33 -0800
To: Thomas Roessler <tlr@w3.org>, Max Froumentin <maxfro@opera.com>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D312D659F4D8@orsmsx501.amr.corp.intel.com>
Some ideas around use cases for CPU frequency are:
- Maybe your web appl can provide some advanced features if you are running on a fast device?
- Maybe your web appl needs more power to do a certain task, so you bump up the CPU freq? similar to burst mode.

Dzung Tran, Intel Corp

-----Original Message-----
From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Thomas Roessler
Sent: Tuesday, January 05, 2010 08:25 AM
To: Max Froumentin
Cc: Thomas Roessler; public-device-apis@w3.org
Subject: CPU API (Re: [sysinfo] draft ready for review)

A few comments:

- What's our use case for inquiring about CPU frequency?
- What's our use case for *setting* CPU frequency from a Web application?
- CPU load (and detailed power consumption along with it) can be a data leak.  I'd like the spec to be clear that this value will generally be an average taken over time, and I'd like the spec to caution against just making this information available.

Thomas Roessler, W3C  <tlr@w3.org>

On 18 Dec 2009, at 13:27, Max Froumentin wrote:

> Hi WG,
> As promised on Wednesday, I'm submitting a SysInfo draft for review. It is at: http://dev.w3.org/2009/dap/system-info/
> Max.
Received on Wednesday, 6 January 2010 00:04:37 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:41 UTC