You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by bu...@apache.org on 2004/09/27 07:34:56 UTC

DO NOT REPLY [Bug 31432] New: - caching point pipelines and smart caching

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=31432>.
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=31432

caching point pipelines and smart caching

           Summary: caching point pipelines and smart caching
           Product: Cocoon 2
           Version: 2.1.5
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: general components
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: oliver.powell@tvnz.co.nz


I think if you choose to use caching-point type caching, then smart-caching
should effectively be automatically turned off. Or, in other words, I would
expect when using the caching-point pipeline processor that it would by default
behave as it does when smart-caching is off: which is to always look for shorter
keys in the cache if a response is not found for the current key combination.

Perhaps this could be implemented by having CachingPointProcessingPipeline
override the validatePipeline method to make it always try shorter keys (at the
same time, remove this functionality from the AbstractCachingProcessingPipeline).