On 8/1/12 11:44 AM, Glenn Maynard wrote:
Ideally, a new responseType could be added to XHR which operates like "blob", except instead of reading the whole resource, it just performs a HEAD to retrieve the response length and immediately returns the Blob, which can be read to perform further Content-Range reads.
Unless the server is one of the common ones with broken HEAD handling. Or unless the resource is served with Content-Encoding:gzip, in which case your Content-Range is all sorta broken. :(
The trouble is chunked responses, where the length of the resource isn't known in advance, since Blobs have a static length and aren't designed for streaming.
That's another trouble, yes. -Boris
