DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31234>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31234 Event Aware cache does not remove registry key ------- Additional Comments From [EMAIL PROTECTED] 2004-09-23 06:03 ------- If anyone's interested... the btw issue at the end of my original posting of this bug, about processEvent() calling cache remove preventing you from taking advantage of caching-point functionality, has been resolved simply by switching OFF "smart-caching" for the pipeline component in the sitemap (CachingPointProcessingPipeline). So it is NOT A BUG. If smart-caching is ON (which is the default setting), the processing pipeline DOES NOT try a shorter key. It only does if smart-caching is switched OFF, eg: <map:pipe name="event-aware" src="org.apache.cocoon.components.pipeline.impl.CachingPointProcessingPipeline"> <parameter name="cache-role" value="org.apache.cocoon.caching.Cache/EventAware"/> <parameter name="smart-caching" value="false"/> </map:pipe> There has already been some debate in bug #25887 over whether the cache is actually being smarter when smart-caching=false... I guess there is more looping going on when smart-caching=false, which might be a waste of time if your content is always fully un-cached or fully cached (no half-pipelines cached) - so sometimes turning off smart-caching might not be a good idea? Cheers
