Re: Lazy Blob

On Wed, Aug 1, 2012 at 8:16 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> 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.  :(


Those could fall back on fetching the whole resource, too, so these issues
would still be transparent to scripts (if the broken HEAD cases are
detectable, anyway).  gzip/deflated content could still work (without
fetching the entire resource) in the common case of reading a Blob
sequentially.  It'd only need to fall back on retrieving the entire
resource if you're doing nonsequential reads.

It's not ideal, but it doesn't seem like such a big problem that it'd make
the feature not worth it.

It still doesn't help the "creating lots of resources without making lots
of network requests" use case, though.

-- 
Glenn Maynard