Hi Kyle,

What I image about WebUSB is just there is a way for communicating between 
external device and Web Apps.
So there will be 

  1. a generic USB driver for exposing USB dev node to userspace.
  2. a Gecko component / Web API to provide a way for connecting Web Apps & USB 
dev node.
  3. a communicating protocol through exposed dev node.

Then the data flow will just be happened between external device and Web Apps 
and what function will be provided by Web Apps is through standard Web API too.
Based on this model, may I know what security issue needed to be considered.

Ex: A USB camera can be connected to Fx OS device and a corresponding Web Apps 
can act as a camera app by WebUSB and other Web APIs (media stream, canvas, 
image and others).

----------------------------------------------------------------------

About the libusb and libusbhost you mentioned is about whether FxOS device acts 
as a USB Host or Client mode.
And it is related to the power source and enumeration control, I think it is 
not directly related to WebUSB.

Thanks,
Sincerely yours.                                         


----- 原始郵件 -----
寄件者: "Kyle Machulis" <[email protected]>
收件者: "Fabrice Desre" <[email protected]>
副本: "Marco Chen" <[email protected]>, "jose llopis" <[email protected]>, 
"Mozilla" <[email protected]>
寄件備份: 2013 8 月 20 星期二 上午 2:50:05
主旨: Re: [b2g] SerialPort communication?

Profiles are bluetooth, not USB. While there are device classes in USB (HID, 
USB Audio, storage, etc), it's still different than BT profiles.

WebUSB did have some initial implementation in summer of 2011, but that's all 
seriously bitrotted now and was aimed for desktop. For generic USB on FxOS, 
we'd need a OOP'd DOM API, then a layer to hook it up to Android's libusbhost 
library (which looks like libusb but not quite). This is by no means trivial 
work, since we'd need to figure out exactly what parts of USB we wanted to 
support (Just simple interrupt/bulk? Full isochronous support to write frames 
to a canvas? Supporting some device classes across the whole system?), security 
would be a nightmare, etc. Not saying it can't be done, it's just a long way 
off.

----- Original Message -----
> From: "Fabrice Desre" <[email protected]>
> To: "Marco Chen" <[email protected]>
> Cc: "jose llopis" <[email protected]>, "Mozilla" 
> <[email protected]>
> Sent: Monday, August 19, 2013 8:38:01 AM
> Subject: Re: [b2g] SerialPort communication?
> 
> Hi Marco,
> 
> On 08/19/2013 07:54 AM, Marco Chen wrote:
> > Hi Jose,
> > 
> > There is a "Bug 674718 - (webusb) WebUSB" for what you want, but it is
> > pending now.
> > 
> > Hi all,
> > 
> > I saw some discussion on the development for userspace.
> > May I know whether we need a generic USB driver with generic Mozilla
> > protocol for communicating between web app and external USB device?
> 
> I think we need a way to let profiles be implemented in content JS, if
> this is what you mean or is this covered by bug 674718 ?
> 
>       Fabrice
> --
> Fabrice Desré
> b2g team
> Mozilla Corporation
> _______________________________________________
> dev-b2g mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-b2g
> 
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to