W3C home > Mailing lists > Public > public-html-media@w3.org > October 2014

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

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Wed, 15 Oct 2014 18:39:35 +0000
To: Domenic Denicola <domenic@domenicdenicola.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: <39a3aea11eb44f24992b6fb52b775fde@BL2PR03MB418.namprd03.prod.outlook.com>
> The decision we came to in web apps some months ago was that the interfaces in that spec would disappear in favor of WritableStream, ReadableStream, and the rest.

This seems to contradict the direction that was published in Feb 2014 [1] in which it was clearly stated:

" In addition to the base Stream spec, the remaining platform-specific pieces which do not fit into the shared-base spec will live in an independent spec. This includes things such as support in other APIs (XHR, MediaStreaming, etc) or DOM specific scenarios - (createObjectURL()). The current W3C Streams API will focus on this aspect of the API surface, while leaving the core functionality to be defined in the base spec."

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

/paulc

[1] http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0218.html 


Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

-----Original Message-----
From: Domenic Denicola [mailto:domenic@domenicdenicola.com] 
Sent: Wednesday, October 15, 2014 2:25 PM
To: Paul Cotton; Takeshi Yoshino
Cc: Jerry Smith (WINDOWS); Anne van Kesteren; public-webapps; Arthur Barstow; Feras Moussa; public-html-media@w3.org; Aaron Colwell
Subject: RE: [streams-api] Seeking status of the Streams API spec

From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] 

> Would it be feasible to resurrect this interface as a layer on top of [1] so that W3C specifications like MSE that have a dependency on the Streams interface are not broken?

The decision we came to in web apps some months ago was that the interfaces in that spec would disappear in favor of WritableStream, ReadableStream, and the rest. The idea of a single Stream interface was not sound; that was one of the factors driving the conversations that led to that decision.

Received on Wednesday, 15 October 2014 18:40:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:55 UTC