- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Tue, 1 Oct 2013 14:46:50 -0700
- To: Rob Manson <roBman@mob-labs.com>
- Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>, "public-ar@w3.org" <public-ar@w3.org>
On 29 September 2013 17:36, Rob Manson <roBman@mob-labs.com> wrote: > I drew this diagram recently in an attempt to put together a clear picture > of how all the flows work/could work together. It seems to resonate with > quite a few people I've discussed it with. I don't think that this is the right way to present this information. This isn't just because of the problems that Harald found with the Stream <=> MediaStream analogy. The fundamental problem is that you are mixing primitives (MediaStream/Track) with sources and sinks (like gUM, RTCPeerConnection, processing nodes, audio and video tags). At least for media, there should be primitives on either side of the processing and RTC nodes (RTCPeerConnection, web audio). And a similar set of nodes would isolate byte streams from media streams, the MediaRecorder being one example of this.
Received on Tuesday, 1 October 2013 21:47:17 UTC