- From: Paul Cotton <Paul.Cotton@microsoft.com>
- Date: Mon, 13 Oct 2014 18:52:52 +0000
- To: Domenic Denicola <domenic@domenicdenicola.com>, Takeshi Yoshino <tyoshino@google.com>
- CC: public-webapps <public-webapps@w3.org>, Arthur Barstow <art.barstow@gmail.com>, Feras Moussa <feras.moussa@hotmail.com>
> old specs that had their own custom stream-ish objects will over time upgrade MSE [1] simply used the "Stream" object directly from the previous W3C WD [2]. Since this object no longer is available in [3], what you do recommend that MSE should do? /paulc [1] http://www.w3.org/TR/2014/CR-media-source-20140717/#sourcebuffer-stream-append-loop [2] http://www.w3.org/TR/2013/WD-streams-api-20131105 [3] https://streams.spec.whatwg.org/ 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: Monday, October 13, 2014 2:40 PM To: Paul Cotton Cc: public-webapps; Arthur Barstow; Takeshi Yoshino; Feras Moussa Subject: RE: [streams-api] Seeking status of the Streams API spec Good question. Takeshi should weigh in on this too since he has been doing some of the integration work. In general, the idea is for streams, like promises, to be a base primitive which many other specifications create instances of. Since the spec is focused on defining that primitive, it doesn't include an informative list of specs that could potentially use it; we left that for non-spec material. But in general the way we envision this working is much like with promises: new specs that include streaming data will reach around for the right primitive, and find streams; old specs that had their own custom stream-ish objects will over time upgrade; and all the while, developers will be prototyping and creating their own streams (some of which might wrap existing APIs) using the stream constructors. We as editors will be helping reach out and guide those efforts, as we've done with promises. Currently there are efforts ongoing with Fetch (XHR replacement) and Web Audio as the trailblazers, with more certainly to come. Hope that helps, -Domenic -----Original Message----- From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] Sent: Thursday, October 9, 2014 19:04 To: Domenic Denicola Cc: public-webapps; Arthur Barstow; Takeshi Yoshino; Feras Moussa Subject: RE: [streams-api] Seeking status of the Streams API spec The previous W3C WD [1] identified a large number of specifications that were stream producers and consumers. Is there any kind of mapping of the interfaces in the previous W3C WD to your recent specification to give all of those other specifications some idea of how to change to align with the new Streams specification? /paulc HTML WG co-chair [1] http://www.w3.org/TR/2013/WD-streams-api-20131105/#producers-consumers 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: Thursday, October 09, 2014 4:24 PM To: Paul Cotton Cc: public-webapps; Arthur Barstow; Takeshi Yoshino; Feras Moussa Subject: RE: [streams-api] Seeking status of the Streams API spec From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] > Was this Aug goal achieved? Yes: https://streams.spec.whatwg.org/
Received on Monday, 13 October 2014 18:53:21 UTC