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

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

From: Max Froumentin <maxfro@opera.com>
Date: Wed, 06 Jan 2010 13:05:42 +0100
Message-ID: <4B447C96.6000209@opera.com>
To: Thomas Roessler <tlr@w3.org>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
On 06/01/2010 12:17, Thomas Roessler wrote:
> Why is "machine is in a dangerous state" the webapp author's concern,
> and not the runtime's?  The same comment as for the CPU API -- what's
> our abstraction model here? -- applies.

The same webapps/runtime comments apply across the whole specification, 
and the whole of DAP!

In this case, there are scenarios in which the webapp author is 
concerned that his webapp is using too many resources and wants to react 
accordingly (slowing down the frame rate, for instance)

Of course you could simplify things drastically and provide a single API 
that has one attribute that exposes the "system stress", combining CPU, 
thermal, fans, etc. Is that what people expect from a System Information 

Received on Wednesday, 6 January 2010 12:06:17 UTC

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