Storing partial responses

Hi everyone,
    I've added a new branch on sourceforge for working on storeing and returning HITS from partial responses. I don't know how fast
I'll move it along :]. If anyone wants to collaborate on it then fantastic.

for reference, the tag is storepartial.

My rough approach plan is to
a) get strong validation working. (if it's not already)
b) figure out how best to store multiple sections from a URL in the object store. IE should we consider each non-overlapping range a
separate URI? Or perhaps store a series of sections in the ondisk object with common details in the meta data and then 1..n sections
of defined length and offset? I haven't put a great deal of effort into this, and I'm hoping to avoid invalidating the existing
caches when it happens.
c) get squid caching the partial responses and serving hits that are completely covered by in-cache range data.
d) look into extra optimisations (for example, if we have a partial response in cache, ask the origin for a HEAD, and if a strong
validator comparison succeeds send one or more range requests to the origin, fulfilling the client from the store and from the
origin.)

Rob
Received on Mon Dec 11 2000 - 23:59:16 MST