Re: Streams and Blobs

On Tue, Feb 26, 2013 at 7:53 AM, Glenn Maynard wrote: > On Tue, Feb 26, 2013 at 4:56 AM, Anne van Kesteren wrote: > >> The advantage the Streams API seems to have over moz-blob is that you > > do not need to create a new object to read from each time there's >> fresh data. The disadvantage is tha

Re: [XHR] chunked

On Thu, Sep 27, 2012 at 12:21 PM, Travis Leithead < travis.leith...@microsoft.com> wrote: > > From: annevankeste...@gmail.com [mailto:annevankeste...@gmail.com] > > > > On Thu, Sep 27, 2012 at 7:42 PM, Travis Leithead > > wrote: > > > In my observation of the current IE behavior, the Stream is fo

Re: [XHR] chunked

On Thu, Sep 27, 2012 at 12:21 PM, Travis Leithead < travis.leith...@microsoft.com> wrote: > > From: annevankeste...@gmail.com [mailto:annevankeste...@gmail.com] > > > > On Thu, Sep 27, 2012 at 7:42 PM, Travis Leithead > > wrote: > > > In my observation of the current IE behavior, the Stream is fo

Re: [XHR] chunked

On Thu, Jun 7, 2012 at 3:11 AM, Anne van Kesteren wrote: > On Thu, Jun 7, 2012 at 11:48 AM, Wenbo Zhu wrote: > > I suppose you still favor the idea of exposing chunked HTTP to > > applications. Without it, native clients will be increasingly deployed > > in place of HTM

Re: [XHR] chunked

On Thu, Jun 7, 2012 at 2:34 AM, Anne van Kesteren wrote: > On Thu, Jun 7, 2012 at 11:30 AM, Wenbo Zhu wrote: >> Yes, this will be the desired behavior. > > Can I take this as Chrome being interested in implementing the chunked > proposal as well? Will have to get back to you o

Re: [XHR] chunked

On Thu, Jun 7, 2012 at 2:14 AM, Henri Sivonen wrote: > On Thu, May 24, 2012 at 8:59 AM, Anne van Kesteren > wrote: > > On Thu, May 24, 2012 at 2:54 AM, Jonas Sicking wrote: > >> Is there a reason not to add "chunked-text" and "chunked-arraybuffer" > >> to the spec right now? > > > > 1. Why not

Re: [XHR] chunked requests

On Thu, Dec 8, 2011 at 2:36 PM, Charles Pritchard wrote: > > > > > On Dec 8, 2011, at 1:04 PM, Wenbo Zhu wrote: > > > > On Wed, Dec 7, 2011 at 6:04 PM, Charles Pritchard < > ch...@jumis.com> wrote: > >> ** >> I think the Web Sockets spec is

Re: [XHR] chunked requests

ing to do with either HTTP or WebSocket. I don't know that arbitrary binary data is on their agenda -- I hope it is > -- for p2p communication. > > > > On 12/7/11 5:59 PM, Wenbo Zhu wrote: > > One use case that we have which is not currently handled by XMLHttpRequest > is

[XHR] chunked requests

One use case that we have which is not currently handled by XMLHttpRequest is incrementally sending data that takes a long time to generate _from the client to the server_. For example, if we were to record data from a microphone, we couldn't upload it in real time to the server with the current AP

Re: [XHR] chunked

On Wed, Nov 30, 2011 at 7:28 AM, Anne van Kesteren wrote: > A while ago sicking proposed adding chunked support to XMLHttpRequest: > > http://lists.w3.org/Archives/**Public/public-webapps/** > 2011JulSep/0741.html > https://

Re: [XHR2] Streamed send or receive

t 6, 2011 at 10:57 AM, Wenbo Zhu wrote: > > I'd like to hear from the WG if the following use cases or issues have > been > > discussed before. > > 1) When onreadystatechange is invoked as new response data is being > > received, currently there is no way to clear a

Re: [XHR2] Streamed send or receive

Sorry, the API for 2) should read: SendPartialRequest(). On Thu, Oct 6, 2011 at 12:57 AM, Wenbo Zhu wrote: > I'd like to hear from the WG if the following use cases or issues have been > discussed before. > > 1) When onreadystatechange is invoked as new response data is

[XHR2] Streamed send or receive

I'd like to hear from the WG if the following use cases or issues have been discussed before. 1) When onreadystatechange is invoked as new response data is being received, currently there is no way to clear any buffered responseText (alike) that has already been consumed. The lack of such a capabi