W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

Re: Lazy Blob

From: Glenn Maynard <glenn@zewt.org>
Date: Wed, 1 Aug 2012 20:50:04 -0500
Message-ID: <CABirCh_TKtYeCNVutCZBXDs=B9k4JvUHibWmPNoGkbuFeiQEtA@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-webapps@w3.org
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
Received on Thursday, 2 August 2012 01:50:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:37 UTC