- From: Domenic Denicola <domenic@domenicdenicola.com>
- Date: Tue, 14 Oct 2014 16:19:41 +0000
- To: Aaron Colwell <acolwell@google.com>
- CC: Anne van Kesteren <annevk@annevk.nl>, Paul Cotton <Paul.Cotton@microsoft.com>, Takeshi Yoshino <tyoshino@google.com>, 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>
From: Aaron Colwell [mailto:acolwell@google.com] > Yes SourceBuffer is shipping and has been for quite some time in Chrome and IE. Hmm, window.SourceBuffer is undefined in Chrome. > I am NOT going to rework it all to be a WritableStream. That's a shame, but completely understandable that you wouldn't want to be one of the early-adopters. Over time we'll work to convert to using streams (in an integrated way) across the ecosystem, but I understand this will involve a lot of legwork from my side and from the streams implementers (e.g. the Tokyo team at Google). > I am just looking to adjust appendStream() to take whatever object replaced the old Stream object that was in the original. It sounds like this is ReadableStream so I'll take a look at the latest spec text and update MSE accordingly. I would suggest just removing appendStream, personally. It does not seem to carry its own weight given that it is non-compositional with the rest of the stream ecosystem. As an analogy, this would be like adjusting a callback-taking method to wait for any promises its callbacks return, without actually converting the method to be promise-returning. In other words, a very halfhearted integration of a less-important part of the promise ecosystem, ignoring the more important part that allows developers to use the method seamlessly. It would be better to wait for a "v2" of MSE that can integrate streams more correctly, than to tack on appendStream, IMO.
Received on Tuesday, 14 October 2014 16:20:13 UTC