- From: Rich Tibbett <richt@opera.com>
- Date: Mon, 04 Oct 2010 13:43:58 +0200
- To: W3C Device APIs and Policy WG <public-device-apis@w3.org>
I managed to get some review of the current spec done. The API looks good. One concern is that some properties seem to add a lot of overhead to sensor calculations. In the Network ConnectionAttributes interface, returning upload/download bandwidth constraints may require speed tests to be run from the device - that might make for some overhead. Instead, perhaps the network connection info currently implemented in Android (navigator.connection.type) may be enough in a first version. A developer can deduce certain speed and pricing characteristics from being on a WIFI, EDGE, UMTS or a GPRS connection. The SuccessCB and ErrorCB interfaces should de-camelCase the onX to onx in line with the HTML5 style. So onSuccess should become onsuccess and onError should become onerror. Additionally, the EventSource integration will need to be added to these interfaces with their event handler attribute and event handler event type declared in the specification (I beleive Robin is working on this). It would be good to add some non-normative guidelines for user interaction, particularly pertaining to the groups and group levels defined in section 3.1. That's about it for now. - Rich
Received on Monday, 4 October 2010 11:45:07 UTC