[whatwg] Bluetooth devices

Jeremy Orlow jorlow at chromium.org
Thu Aug 19 07:30:43 PDT 2010


Agreed.  Serial is the only case where it might make sense (if you were
making a web version of hyperterminal).

J

On Thu, Aug 19, 2010 at 1:52 PM, David Singer <singer at apple.com> wrote:

> I am not sure whether the physical connectivity used has much bearing on
> what devices are connected and usable, honestly.  Why does the 'virtual'
> wire matter? (USB, serial, Bluetooth, built-in, IEEE4888, ....)?
>
>
> On Aug 19, 2010, at 14:28 , Bjartur Thorlacius wrote:
>
> >> Is there any intention to provide access to Bluetooth devices through
> the
> >> Device element?
> > Addressing Bluetooth specifically might or might not be out of scope
> > of the <device> element, depending on what the scope will be :)
> >
> > This is to low level for my taste; what would a web page want direct
> > communication over Bluetooth for? If RS-323 will be left out, Bluetooth
> > probably should be [left out] too. Higher level JavaScript interfaces
> > for accessing filesystems and user selected audio streams cover all use
> > cases I can think of.
> >
> > But then, I don't fully understand what use cases <device> is trying to
> > solve in the first place.
>
> David Singer
> Multimedia and Software Standards, Apple Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100819/c778ad46/attachment-0002.htm>


More information about the whatwg mailing list