You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org> on 2006/02/23 16:16:38 UTC

[jira] Assigned: (COCOON-1279) caching point pipelines and smart caching

     [ http://issues.apache.org/jira/browse/COCOON-1279?page=all ]

Jean-Baptiste Quenot reassigned COCOON-1279:
--------------------------------------------

    Assign To: Jean-Baptiste Quenot  (was: Cocoon Developers Team)

> caching point pipelines and smart caching
> -----------------------------------------
>
>          Key: COCOON-1279
>          URL: http://issues.apache.org/jira/browse/COCOON-1279
>      Project: Cocoon
>         Type: Improvement
>   Components: - Components: Avalon
>     Versions: 2.1.5
>  Environment: Operating System: Linux
> Platform: PC
>     Reporter: Oliver Powell
>     Assignee: Jean-Baptiste Quenot
>     Priority: Minor

>
> 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).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira