Re: [webkit-dev] Streams API

2014-11-10 Thread youenn fablet
I opened a meta-bug at https://bugs.webkit.org/show_bug.cgi?id=138561 I also plan to close bugs related to the previous "stream API" proposal (https://bugs.webkit.org/show_bug.cgi?id=110194 and https://bugs.webkit.org/show_bug.cgi?id=110558). 2014-11-03 7:57 GMT+01:00 Benjamin Poulain : > It looks

Re: [webkit-dev] Streams API

2014-11-04 Thread Xabier Rodríguez Calvar
O Lun, 03-11-2014 ás 10:08 +0100, youenn fablet escribiu: > Hi Benjamin, > > > I have two concerns: > > 1) You have many patches waiting for review. I think you need to get better > > communication channels with reviewers in order to iterate over your patches > > faster. It is unfortunate but gett

Re: [webkit-dev] Streams API

2014-11-03 Thread youenn fablet
In any case, ensuring that the streams API works efficiently for HTTP exchanges in WebKit is top priority imho, no matter whether tied to fetch or XHR at the end of the day. 2014-11-02 17:34 GMT+01:00 Anne van Kesteren : > On Sun, Nov 2, 2014 at 2:56 PM, youenn fablet wrote: >> Meaning that only

Re: [webkit-dev] Streams API

2014-11-03 Thread youenn fablet
Hi Benjamin, > I have two concerns: > 1) You have many patches waiting for review. I think you need to get better > communication channels with reviewers in order to iterate over your patches > faster. It is unfortunate but getting complex patches reviewed in WebKit > requires poking reviewers dir

Re: [webkit-dev] Streams API

2014-11-02 Thread Benjamin Poulain
It looks like nobody has raised any concern against Streams API. We even got positive feedback from Anne. :) I have two concerns: 1) You have many patches waiting for review. I think you need to get better communication channels with reviewers in order to iterate over your patches faster. It i

Re: [webkit-dev] Streams API

2014-11-02 Thread Anne van Kesteren
On Sun, Nov 2, 2014 at 2:56 PM, youenn fablet wrote: > Meaning that only the fetch API would at some point support streams? > If so, I wonder why we should postpone a small but useful feature to a > nice but future API. I suspect there will be many APIs that support streams. It's been a sorely mi

Re: [webkit-dev] Streams API

2014-11-02 Thread youenn fablet
Meaning that only the fetch API would at some point support streams? If so, I wonder why we should postpone a small but useful feature to a nice but future API. 2014-10-31 8:48 GMT+01:00 Anne van Kesteren : > On Fri, Oct 31, 2014 at 12:02 AM, youenn fablet wrote: >> I would like to add support fo

Re: [webkit-dev] Streams API

2014-10-31 Thread Anne van Kesteren
On Fri, Oct 31, 2014 at 9:07 AM, Benjamin Poulain wrote: > Any opinion for or against Streams? Do you know if Mozilla intends to > implement it? I'm in favor of having IO streams :-) There's so many features that could be made better by having them. I don't think anyone from Mozilla has looked at

Re: [webkit-dev] Streams API

2014-10-31 Thread Benjamin Poulain
On 10/31/14, 12:48 AM, Anne van Kesteren wrote: On Fri, Oct 31, 2014 at 12:02 AM, youenn fablet wrote: I would like to add support for the streams API, starting with readable streams and their integration with XHR and loaders. This work is expected to happen behind a flag. There's no planned i

Re: [webkit-dev] Streams API

2014-10-31 Thread Anne van Kesteren
On Fri, Oct 31, 2014 at 12:02 AM, youenn fablet wrote: > I would like to add support for the streams API, starting > with readable streams and their integration with XHR and loaders. > This work is expected to happen behind a flag. There's no planned integration with XMLHttpRequest. -- https:/

[webkit-dev] Streams API

2014-10-30 Thread youenn fablet
Hi all, I would like to add support for the streams API ([1], [2]), starting with readable streams and their integration with XHR and loaders. This work is expected to happen behind a flag. Regards, Youenn [1] https://github.com/whatwg/streams [2] http://www.w3.org/TR/streams-api/ ___