Dear cocoon community, FYI, I have submitted a Patch (bugzilla [Bug 10824]) with regards to this [PROPOSAL].
Thanks, Michael Melhem > > From: Michael Melhem [mailto:[EMAIL PROTECTED]] > <snip/> > > > > That's a clever algorithm, but don't you fear it will create too many > > > > branch points (and so cache entries) that what is really required by > > > > the application ? > > > > > > Same fear here. > > > The idea is that whenever the developer feels that cachingpoints would > > be beneficial (perhaps in the case where they use cocoon-views or drill down > > functionality heavily in a pipleline) then they can set that pipeline > > and *only* that pipleine to use caching points. > > > > <map:pipelines default="caching"> > > <map:pipeline name="caching" > > src="org.apache.cocoon.components.pipeline.impl.CachingProcessingPipeline"/> > > <map:pipeline name="cachingpoint" > > src="org.apache.cocoon.components.pipeline.impl.CachingPointProcessingPipeline > > "/> > > </map:pipelines> > > > > Cocoon 2.1 allows one to select the pipeline caching algorithm as above. > > > > This means that the effect of cachingpoint algorithm is localised to where > > its needed. > I know this, and CachingPointProcessingPipeline may be useful in some > situations. > > > PS What was the reason against <map:cache/> proposal in the early days > > > of C2? It seems a bit similar to this caching point stuff. > > > > Im not sure how <map:cache> worked....hmmm, but with cachingpoint > > the caching points are *implicitly* loacted *only* at strategic points > > through out the pipeline, and only if that particular pipeline is > > set to cachingpoint itself. > It never worked, it was proposed once. The idea was to allow developer > to specify caching points. > Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
