W3C home > Mailing lists > Public > public-device-apis@w3.org > February 2013

Processing data: non-DOM

From: Jonathan Chetwynd <jay@peepo.com>
Date: Thu, 07 Feb 2013 10:17:18 +0000
Message-ID: <51137F2E.8000606@peepo.com>
To: public-device-apis@w3.org
Where can one discuss pre-processing data streams using a javascript 
engine if not here?**
How is the author or researcher to process device API data outside the 
browser environment?**

Processing A/V and other data streams,
can be resource intensive.

Intermediate results may not be intended for end-user.

Small, cheap or embedded devices may not be able to process data
& run a browser efficiently in real-time.

for example: webRTC is currently dependent on DOM.

Proposal: The javascript engine should be enabled to process data 
streams independently.


Jonathan Chetwynd

** 2.2
Out of Scope
The definition of a policy framework that would allow using the defined 
APIs into a different security environment than the default browser 
context is out of the scope for this group.
Received on Thursday, 7 February 2013 10:17:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:58 UTC