- From: Rob Manson <roBman@mob-labs.com>
- Date: Sat, 24 Sep 2011 00:30:18 +1000
- To: robert@ocallahan.org
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>, public-audio@w3.org
Hi Rob, I'm not suggesting that the implementations would be the same at all. Yet, from an API users perspective there is a lot of overlap in terms of "being able to access/process the data within a stream/track". Ideally I'd like to just be able to do this in one consistent way across both audio and video and local and remote. One consistent and effective security model while still enabling as much developer power/access as possible. roBman On Sat, 2011-09-24 at 02:14 +1200, Robert O'Callahan wrote: > At first glance this Microsoft proposal is mostly unrelated to the > MediaStreams proposals. Their Streams are simply growable buffers of > binary data, a natural extension of File/Blob. MediaStreams represent > media channels whose contents are managed by the browser in real time. > > Rob > -- > "If we claim to be without sin, we deceive ourselves and the truth is > not in us. If we confess our sins, he is faithful and just and will > forgive us our sins and purify us from all unrighteousness. If we > claim we have not sinned, we make him out to be a liar and his word is > not in us." [1 John 1:8-10]
Received on Friday, 23 September 2011 14:30:57 UTC