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

FW: Update on Streams API Status

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Fri, 7 Feb 2014 14:47:38 +0000
To: "public-html-media@w3.org" <public-html-media@w3.org>
Message-ID: <45438a47f9eb4d9b934b211bfe80b7d2@BL2PR03MB418.namprd03.prod.outlook.com>
FYI.

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

-----Original Message-----
From: Arthur Barstow [mailto:art.barstow@nokia.com] 
Sent: Friday, February 07, 2014 7:58 AM
To: public-html-admin@w3.org
Subject: Fwd: Update on Streams API Status

Since the Media Source Extensions spec includes a normative reference for WebApps' Streams API, please see the following status and plans information from the spec's Editors.

If you have any comments, please send them to <mailto:public-webapps@w3.org>.

-------- Original Message --------
Subject: 	Update on Streams API Status
Resent-Date: 	Fri, 7 Feb 2014 04:31:48 +0000
Resent-From: 	<public-webapps@w3.org>
Date: 	Thu, 6 Feb 2014 20:31:18 -0800
From: 	ext Feras Moussa <feras.moussa@hotmail.com>
To: 	public-webapps@w3.org <public-webapps@w3.org>
CC: 	domenic@domenicdenicola.com <domenic@domenicdenicola.com>, Takeshi 
Yoshino <tyoshino@google.com>


Hi All,
  
I wanted to update everyone on the latest plan for moving forward on the Streams spec.
  
For a variety of reasons, there are currently two Streams Specs being worked on - one in the W3C, and one in the WHATWG. Each of these specs have their strengths and weaknesses, and were looking at problems from different perspectives.
  
After meeting with the WHATWG folks and discussing the various scenarios being targeted by the Streams specs as well as other considerations, we all agreed that we have the same goals and should work together to get alignment and avoid having different implementations.
  
This is an opportunity to get a strong consistent API which behaves similarly across the various platforms, from browsers to servers. We are excited with the potential here, because it lets us tell one story.
  
Moving forward, we've agreed to revise the approach to working on the Streams spec as follows:
  
Create a 'base' Stream spec, which we will work together on. This will be seeded with the base of the WHATWG spec, and we will incorporate various pieces from either spec as needed.
This base Stream should:
1. Be the lowest primitive that is independent of any platform 2. Be a layer that could make it into the JS language/ES 3. Could be prototyped in JavaScript directly to showcase it 4. Supports the various Stream goals we discussed, such as creation, backpressure, read/write behaviors, etc.
  
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.
  
Once we've reorganized the components as defined above, we will share out further details for locations of the specs as well as solicit review.
  
Thanks,
Feras
  
Received on Friday, 7 February 2014 14:48:07 UTC

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