Santiago Gala wrote: > Re: cache comments later: > > When I was discussing Cocoon (then new) cache ideas with Ricardo > Rocha, (so around winter 2000/spring 2001) I sent an idea to Cocoon-dev > about propagating the CacheValidity to set the Expires in the seriazed > output. It looked like a clean (the only clean way I have found to date > in any famework) to set the "expires:" header in a web publishing > framework. AFAIK it got lost in the sea of bits. If any of you set on > fight against the cache, it could be very worthwhile. And I would have > contributed another bits to Cocoon ;-) > In theory it is possible to set the expires header and to propagate the cachevalidity. But (currently) the cachevalidity does not hold any expires information. In most cases it contains a last modification date of the used files (xml/xslt).
Carsten
