Kinda sorta of. I have made a simple diagram with some of this information:
http://people.apache.org/~amc/ats-cache-layout.jpg which you might find useful. The proposed change would be quite similar to the existing cache structure but would have a couple of major differences - 1) Support having "fallow" fragments. The current logic requires all fragments to be present in the cache and cannot detect or handle missing fragments. 2) Subdividing each fragment in to chunks. All of that would be new. This would also require moving the fragment offset data in to the alternate information but I already have a patch for that which will be landing on trunk Real Soon Now. Tuesday, August 28, 2012, 1:14:48 PM, you wrote: > This model of representing a cached object indeed allows holding only > partial data for the resource. > Is this the current way a cached object is currently represented in TS?
