- From: Travis Leithead <travis.leithead@microsoft.com>
- Date: Fri, 15 Feb 2013 18:18:29 +0000
- To: Martin Thomson <martin.thomson@gmail.com>, Johannes Odland <johannes.odland@gmail.com>
- CC: Jonathan Chetwynd <jay@peepo.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Also, the choice of the "navigator" object should not carry too much implied notion that this is a browser-only feature. Navigator already existed (and is the home geolocation too), so we are using it--there's no other particular dependency on this object. For example, nodejs could choose to host this functionality from global or from another object (say "media"). > -----Original Message----- > From: Martin Thomson [mailto:martin.thomson@gmail.com] > Sent: Friday, February 15, 2013 10:04 AM > To: Johannes Odland > Cc: Jonathan Chetwynd; public-media-capture@w3.org > Subject: Re: Why does media capture require a browser? > > node.js has a very different security model, so it is possible that a > completely different API would be appropriate in that context. > > That's not to say that node.js couldn't copy aspects of the API, but > they wouldn't want to be constrained by the necessarily byzantine > selection API we have adopted, at a bare minimum. > > On 15 February 2013 07:53, Johannes Odland <johannes.odland@gmail.com> > wrote: > > I've been asking the same question. > > > > Why can't I use the same API to set up a webcam using Raspberry Pi and > and > > Node.js? > > > > Having an API that does not depend on the DOM/Browser makes it possible > to > > implement that API on multiple platforms such as in the browser and in > > Node.js. > > > > Frameworks written for such an API could be used on all platforms. > > > > As it is right now we have different APIs for capturing and processing > > media. > > > > ( https://github.com/wearefractal/camera library for media capture on > > node.js) > > > > Johannes Odland > > > > Den 15. feb. 2013 kl. 16:18 skrev Jonathan Chetwynd <jay@peepo.com>: > > > > Why does media capture require a browser? > > rather than solely a javascript engine**. > > > > eg why navigator.getUserMedia?* > > > > regards > > > > Jonathan Chetwynd > > > > **embedded devices may only be capable of running a JS engine, with say > > camera, > > but not a browser as well. > > There are of course a very large range of data capture devices beyond > A/V. > > > > *for example nodeJS using V8 has no navigator object. > > > > > > -- > > Jonathan Chetwynd > > http://www.gnote.org > > Eyetracking in HTML5 > > > >
Received on Friday, 15 February 2013 18:19:23 UTC