Dear Cocoon Gods, (Flattery will get you everywhere!) In Particular: Attn: Sylvain Wallez Attn: Carsten Ziegeler
FYI, I have been working to complete "cachingpoint" (CP) pipelines so that auto CP (ACP) is fully functional (and capable of supporting manual cachingpoint). Changes include: 1. Cachingpoint pipeplines implement configurable. So its now possible to switch between cachingpoint policies easly. <map:pipeline name="cachingpoint" src="...impl.CachingPointProcessingPipeline"> <cachingpoint-policy>...AutoCachingPointStrategy</cachingpoint-policy> <!-- cachingpoint-policy>...ManualCachingPointStrategy</cachingpoint-policy --> </map:pipeline> 2. Introduced a new TreeProcessor Node called SimpleLeafProcessingNode.java (as opposed to SimpleParentProcessingNode). SimpleLeafProcessingNode groups the common cocoon-views behavior at higher level and makes it easier support manaul cachepoints etc. Thoughts, comments ? :-P THOUGHTS ON MANUAL CACHINGPOINTs (MCPs). Does it make sense to have a MCP on anything other than "Leaf" Nodes? That is, Nodes which dont subclass SimpleParentProcessingNode? As with cocoon-views, I would say the answer is *no*.. ParentProcessingNodes are not candidates for MCP's) The current cachingpoint behavior flags a cachingpoint whenever a "leaf" node is indicated to have one or more "views". So in effect, we already have a mechansim for manual cachingpoint (well close, you still need to have a view defined). I was thinking that one possibility is to extend this "views" behavior so you can have something like the following: <map:transform src="../simple-samples2html.xsl" label="cachingpoint"/> Where in effect, you manually label a pipeline component as being a cachingpoint. In this case, "cachingpoint" is not a view but a "resevered" word to indicate that this component is a manual cachingpoint. After this fashion, you can also label components as manual "cachingpoints" within the <components> section of the sitemap.xmap (as with cocoon-views) (alternatively you can seperate the concerns by having something like <map:transform src="../simple-samples2html.xsl" cachingpoint="true"/>) Any thoughts on this? Best Regards, Michael Melhem --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]