W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

Re: Update on Streams API Status

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 7 Feb 2014 10:52:54 +0100
Message-ID: <CADnb78jPUDg2X_+-Q3oxqiNdrA2gc2geAUHgcVsGagi0hsUv2w@mail.gmail.com>
To: Feras Moussa <feras.moussa@hotmail.com>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>, "domenic@domenicdenicola.com" <domenic@domenicdenicola.com>, Takeshi Yoshino <tyoshino@google.com>
On Fri, Feb 7, 2014 at 5:31 AM, Feras Moussa <feras.moussa@hotmail.com> wrote:
> 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.

Sounds great, thanks guys!

As for createObjectURL(), it has not been a great success for Blob
objects. I'm not really sure we should widen that experiment. At least
not until the way they are supposed to be implemented for Blob objects
has actually been done in practice.

Received on Friday, 7 February 2014 09:53:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:21 UTC