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

[whatwg] Bluetooth

From: Diogo Resende <dresende@thinkdigital.pt>
Date: Thu, 2 Dec 2010 14:50:07 +0000
Message-ID: <1291301407.18026.8.camel@nasgul>
This is exactly my point (and probably Don). I was not thinking about
common i/o devices. I was thinking about a way to somehow connect to an
uncommon device. Maybe something like websockets, maybe devsockets :P

I can see 3 important steps to do this:

- have a way expose diferent devices (so the app can search/list)

- have permission to access a specific device (yes/no/remember)
  (the browser should do the bluetooth pairing stuff)

- talk to the device with some kind of stream/socket

Does anyone think this could be a good idea?


On Thu, 2010-12-02 at 15:10 +0100, Anne van Kesteren wrote:
> On Thu, 02 Dec 2010 15:05:06 +0100, Diogo Resende  
> <dresende at thinkdigital.pt> wrote:
> > What about having the possibility to "use" a device other than a video?
> > Maybe a specific hardware. I agree about not having a distinction on the
> > hardware stack being used, but there should be a way for an app to be
> > able to access an USBx/BT/FW device.
> Ideally we can have some abstract layer -- so type of hardware does not  
> need to be exposed -- that JavaScript can script against. Not sure how  
> feasible that is though. It would be quite cool if all kinds of devices  
> such as game controllers, medical devices, etc. can be connected in a  
> browser-agnostic way (i.e. no extensions) and the page could provide the  
> implementation. Seems somewhat far away though. :-)
Received on Thursday, 2 December 2010 06:50:07 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:28 UTC