- From: Matthew Wolenetz <wolenetz@google.com>
- Date: Mon, 13 Apr 2015 13:34:33 -0700
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: Aaron Colwell <acolwell@google.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>, WHATWG <whatwg@whatwg.org>, Brad Hill <hillbrad@gmail.com>, Ryan Sleevi <sleevi@google.com>, "public-html-media@w3.org" <public-html-media@w3.org>
On Fri, Apr 10, 2015 at 11:11 PM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Sat, Apr 11, 2015 at 12:24 AM, Matthew Wolenetz <wolenetz@google.com> > wrote: > > After further internal discussion, we believe we can and should reuse > > appendStream() rather than adding appendResponse(). > > For those not privy, could you share the reasoning? > Certainly. As I understand it, the reasons for reusing appendStream() rather than adding appendResponse() to MSE are generally two-fold: a) MSE already has appendStream(). In combination with the other changes to Streams API, Fetch, and Mixed Content specs, as well as the known work to update MSE spec to use ReadableByteStream ( https://www.w3.org/Bugs/Public/show_bug.cgi?id=27239), the scope of further changes to existing MSE appendStream() spec are expected to be significantly less than adding a distinct appendResponse() method to MSE. b) We think these other specs (Streams API, Fetch, Mixed Content) are likely to incorporate these changes anyway. Matt
Received on Monday, 13 April 2015 20:35:20 UTC