Content-Encoding and storage forma

So far, there is one difficult and thought-provoking question about
this design: object storage format. Should it be stored encoded once
an encoding is done (using Vary headers to figure out circumstances,
as in the spec)? Should it stay decoded like today, and always be
reencoded during transfer? Or should both formats be available once
created?

Joe likes the idea of both encoded and decoded formats being available
on-disk. Disk space is certainly cheap, and it would save Squid
cycles. It might raise the memory footprint, depending on the design
that falls out. Does this sound good to you guys?

Now, storing both encoded and decoded does present the challenge of
linking for synchronization purposes all encodings of a particular
object. Joe says you guys had already done something like that in
implemting Vary functionality. Are there ideas / code along these
lines that I can glom onto?

                                                Jon
Received on Thu Feb 26 2004 - 00:32:57 MST