[Bug 23720] New: Make it able to issue multiple write()s on a Stream without waiting for completion

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23720 Bug ID: 23720 Summary: Make it able to issue multiple write()s on a Stream without waiting for completion Product: WebAppsWG Version: unspecified Hardware: All

[Bug 23719] New: Consider adding pull style flow control method to Stream

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23719 Bug ID: 23719 Summary: Consider adding pull style flow control method to Stream Product: WebAppsWG Version: unspecified Hardware: All OS: All

[Bug 23718] New: Stream interface should be decoupled into WritableStream and ReadableStream

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23718 Bug ID: 23718 Summary: Stream interface should be decoupled into WritableStream and ReadableStream Product: WebAppsWG Version: unspecified Hardware: All O

Re: CfC: publish WD of Streams API; deadline Nov 3

The main difference is that you are explaining in details what you are doing and the current draft does not, I will look more closely and comment, I am not sure the ES style really helps everybody understanding it. Regards, Aymeric Le 04/11/2013 09:52, Domenic Denicola a écrit : From: Arthur

Re: Thoughts behind the Streams API ED

On Tue, Nov 5, 2013 at 2:11 AM, Takeshi Yoshino wrote: > > Feedback on "Overlap" thread, especially Issac's exhaustive list of > considerations > Deleted citation by mistake. [1] is the Issac's post. > [1] > http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0355.html >

Thoughts behind the Streams API ED

I'd like to summarize my ideas behind this API surface since the overlap thread is too long. We'll put these into bug entries soon. Feedback on "Overlap" thread, especially Issac's exhaustive list of considerations and conversation with Aymeric were very helpful. In reply to his mail, I drafted my

Need review for changes to some html/webapps tests

As part of the work to make the testsuite self hosting, I have made changes to a number of testsuites to remove the dependence on PHP and eliminate hardcoded server names. These changes touch a variety of testsuites that I don't own and need careful review. If possible I would like to complete

[xhr-1] Keep the responseType "json"

> -Original Message- > From: Jungkee Song [mailto:jungkee.s...@samsung.com] > Sent: Wednesday, October 30, 2013 9:48 PM > > As planned, we editors prepared XMLHttpRequest Level 1 [1] as a > Recommendation track version. Initially, we'd planned to put together a > draft with only the parts

RE: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?

Hi. Art. > -Original Message- > From: Arthur Barstow [mailto:art.bars...@nokia.com] > Sent: Friday, November 01, 2013 9:09 PM > To: public-webapps; public-sysa...@w3.org; Marcos Caceres > Subject: Re: [coord] Is there still a need for WebApps + SysApps meeting > at TPAC? > > On 10/31/13 8

RE: CfC: publish WD of Streams API; deadline Nov 3

From: Arthur Barstow [mailto:art.bars...@nokia.com] > Domenic - Mike Smith mentioned you have worked on a related spec. What is the > URL? We are working on a streams specification which addresses the appropriate requirements at https://github.com/whatwg/streams. It is still a work in progress

Re: CfC: publish WD of Streams API; deadline Nov 3

Yes for the different questions, I first mentioned it in [1] That's not an invention of mine, node is doing this: var handle=function(req,res) { var raw=fs.createReadStream(file); res.writeHead(200,head); //and the magic comes here: raw.pipe(zlib.createGzip()).pipe(res); }; h

Re: CfC: publish new WD of Quota Management API; deadline November 3

On Tue, Oct 29, 2013 at 9:01 PM, Arthur Barstow wrote: > Kinuko has made substantive changes [1] to the Quota Management API since > the FPWD was published. As such, this is a Call for Consensus to publish a > new Working Draft using the ED as the basis: > >