- From: Ilkka Oksanen <Ilkka.Oksanen@nokia.com>
- Date: Mon, 11 Jan 2010 13:32:56 +0200
- To: ext Kenton Varda <kenton@google.com>
- CC: Doug Turner <w3c@dougt.org>, Ian Hickson <ian@hixie.ch>, Adam Barth <w3c@adambarth.com>, "Hirsch Frederick (Nokia-CIC/Boston)" <Frederick.Hirsch@nokia.com>, "ext Mark S. Miller" <erights@google.com>, W3C Device APIs and Policy WG <public-device-apis@w3.org>, Ashok Malhotra <ashok.malhotra@oracle.com>
ext Kenton Varda wrote: > On Fri, Jan 8, 2010 at 6:02 PM, Doug Turner <w3c@dougt.org > <mailto:w3c@dougt.org>> wrote: > > Another benefit, although a implementation detail and I am somewhat > skeptical if it will happen, is that it would allow 3rd parties to > add in new devices without having to know much about the internal > browser guts. The work of implementing device apis could move out > of the browser space and could be provided by and supported by > operating system vendors. > > > I agree, this is a *huge* benefit, and one I personally intend to take > advantage of if available (for a personal project involving home > automation). It's vastly easier to understand how to write a local web > server than how to hack your web browser. In some cases one option to implement pure JS based device APIs is to build new browser plug-ins. Hacking of browser core is not therefore always mandatory. There might be still differences in complexity of writing plug-ins and web services but I think they are smaller. -ilkka
Received on Monday, 11 January 2010 11:33:54 UTC