On Mon, 2008-03-17 at 12:05 +0900, Adrian Chadd wrote:
> On Mon, Mar 17, 2008, Robert Collins wrote:
> > On Sun, 2008-03-16 at 14:04 +0900, Adrian Chadd wrote:
> > > Annoyingly, why the hell is the request from the client a range request?
> > > Squid can't easily cache those unless it somehow fetches the entire object
> > > first.
> >
> > FWIW -3 has about 60% of the work needed to cache fragments done. Whats
> > missing is a store that can handle them.
>
> I've looked at the -3 stuff, and its missing about as much as the -2
> stuff is missing. The memory store is only a small part of the overall
> problem handling sparse objects.
>
> (Unless there's some code I've missed that handles other range-request relevant
> stuff.)
In -3 the client side was overhauled to talk in object offsets, so a
range request would ask the store for the relevant bytes, and rather
than getting an opaque stream and range parsing it, it gets the bytes
back; likewise the store insertion by the server side writes offset,
length data into the store, not opaque data.
-Rob
-- GPG key available at: <http://www.robertcollins.net/keys.txt>.
This archive was generated by hypermail pre-2.1.9 : Tue Apr 01 2008 - 13:00:10 MDT