W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2010

[whatwg] Device Element

From: Diego Perini <diego.perini@gmail.com>
Date: Tue, 28 Dec 2010 04:02:29 +0100
Message-ID: <AANLkTin=9YuuAFy51e25H9On_7-8kjgmkMWhzy3UzVpN@mail.gmail.com>
On Tue, Dec 28, 2010 at 3:16 AM, Seth Brown <learc83 at gmail.com> wrote:
> I saw on the spec page that you were considering limiting the device
> element to audio/visual streams. I thinks this would be a mistake.
> I'm currently working on integrating serial port connected hardware
> with a web application I'm developing. The only solution is for the
> user to install local adapter software. This defeats the purpose of
> using a web app over desktop software.
> In order for web applications to be gain traction over desktop
> software, they must be able to interface with usb/RS232. I believe the
> security trade off is worth it.
> I also believe that the working group should make the device element
> spec a high priority. If you don't google will probably implement
> their own version for chrome OS(it will be necessary in a browser
> based OS model).
> Thanks,
> Seth Brown

Agreed. Access to RS232 data from scripts will promote the use of web
technologies in new applications for the embedded market.

Received on Monday, 27 December 2010 19:02:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:02 UTC