> -----Original Message----- > From: Gianugo Rabellino [mailto:[EMAIL PROTECTED] > Sent: Monday, February 24, 2003 5:08 PM > To: [EMAIL PROTECTED] > Subject: Re: CachingProcessingPipeline: new Expires code > > > Carsten Ziegeler wrote: > > > I would say: commit it and we (I?) can review it. > > Done. Fire at will. :-) > > Two things to consider and still on my TODO: > > 1. I understand from AbstractCachingProcessingPipeline that a cache > entry is not going to be built if the generator is not cacheable. Also, > the cache process stops at the first non cachable component in the > pipeline. If that is the case (and indeed it makes sense)
Yes, exactly, this is the way it works. >, then some > more changes are needed to take into account that an expires header is > present: if so, there should be a way to both generate the key and cache > the output and to update/remove entries from the cache if the expires > header is changed or removed from the pipeline. What would be the best > way to do that? I'm thinking about having an object that generates key > on behalf of non cachable components, would that be enough? Hmm, I haven't looked yet into your code. What happens now if an expires date is set, but the pipeline does not have a cacheable generator? Carsten
