- From: Gomer Thomas <gomer@gomert-consulting.com>
- Date: Wed, 16 Mar 2016 12:27:38 -0700
- To: "'Hallvord Reiar Michaelsen Steen'" <hsteen@mozilla.com>
- Cc: "'WebApps WG'" <public-webapps@w3.org>
In my case the object being transmitted is an ISO BMFF file (as a blob), and I want to be able to present the samples in the file as they arrive, rather than wait until the entire file has been received. Regards, Gomer -- Gomer Thomas Consulting, LLC 9810 132nd St NE Arlington, WA 98223 Cell: 425-309-9933 -----Original Message----- From: Hallvord Reiar Michaelsen Steen [mailto:hsteen@mozilla.com] Sent: Wednesday, March 16, 2016 4:04 AM To: Gomer Thomas <gomer@gomert-consulting.com> Cc: WebApps WG <public-webapps@w3.org> Subject: Re: [XHR] On Tue, Mar 15, 2016 at 11:19 PM, Gomer Thomas <gomer@gomert-consulting.com> wrote: > According to IETF RFC 7230 all HTTP recipients “MUST be able to parse > the chunked transfer coding”. The logical interpretation of this is > that whenever possible HTTP recipients should deliver the chunks to > the application as they are received, rather than waiting for the > entire response to be received before delivering anything. > > In the latest version this can only be done for “text” responses. For > any other type of response, the “response” attribute returns “null” > until the transmission is completed. How would you parse for example an incomplete JSON source to expose an object? Or incomplete XML markup to create a document? Exposing partial responses for text makes sense - for other types of data perhaps not so much. -Hallvord
Received on Wednesday, 16 March 2016 19:28:29 UTC