W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2014

RE: [streams-api] Seeking status of the Streams API spec

From: Domenic Denicola <domenic@domenicdenicola.com>
Date: Wed, 15 Oct 2014 18:49:01 +0000
To: Paul Cotton <Paul.Cotton@microsoft.com>, Takeshi Yoshino <tyoshino@google.com>
CC: "Jerry Smith (WINDOWS)" <jdsmith@microsoft.com>, Anne van Kesteren <annevk@annevk.nl>, public-webapps <public-webapps@w3.org>, Arthur Barstow <art.barstow@gmail.com>, Feras Moussa <feras.moussa@hotmail.com>, "public-html-media@w3.org" <public-html-media@w3.org>, Aaron Colwell <acolwell@google.com>
Message-ID: <5802911995a9419081f1349aa435af3e@BY1PR0501MB1477.namprd05.prod.outlook.com>
From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] 

> It seems to me that layering a Stream interface in "an independent spec" would "support other APIs" like MSE.   Why cannot this be done? 

There is no layering to be done here. There are two separate designs: the flawed single-Stream interface, and the multiple-interface ReadableStream and WritableStream designs.

The type of platform-specific pieces referred to were not separate designs like the Stream object, but instead things like how to integrate ReadableStream and WritableStream with Fetch, MSE, Web Audio, etc., or how to add compatibility layers for transitioning between old pseudo-stream interfaces like object URLs and srcObjects to actual streams.
Received on Wednesday, 15 October 2014 18:49:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:31 UTC