- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 16 Apr 2015 19:12:17 +0200
- To: Ryan Sleevi <sleevi@google.com>
- Cc: Aaron Colwell <acolwell@google.com>, WHATWG <whatwg@whatwg.org>, "public-webappsec@w3.org" <public-webappsec@w3.org>, Matthew Wolenetz <wolenetz@google.com>, "public-html-media@w3.org" <public-html-media@w3.org>
I removed some people from the cc. The WHATWG list seems to bite. On Thu, Apr 16, 2015 at 6:57 PM, Ryan Sleevi <sleevi@google.com> wrote: > I think as we look to > provide a compelling story for EME over wholly-proprietary (... rather than > partially-proprietary) solutions, or look to improve the user experience in > streaming video with MSE vs the <video> tag, this is still very much needed. Okay, so accepting that for the moment, that leaves us with deciding on the appropriate API on the MSE side. I don't have a strong preference, but at this point MSE is the only case I can think of that warrants an explicit opaque readable stream class. All the other use cases I have (such as feeding <img> or <script> an arbitrary response) would rather have a Response instance so headers and such are preserved. And that Response can be opaque of course and then (as currently specified) its .body would return null, but these privileged contexts would get access to the underlying body stream. I don't particularly mind introducing an opaque readable stream class, but do we have any other use cases besides MSE? -- https://annevankesteren.nl/
Received on Thursday, 16 April 2015 17:12:44 UTC