Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 90770 invoked by uid 500); 21 Nov 2002 13:59:02 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 90659 invoked from network); 21 Nov 2002 13:58:58 -0000 Message-ID: <3DDCE687.6040801@verizon.net> Date: Thu, 21 Nov 2002 08:58:31 -0500 From: Vadim Gritsenko User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: internal pipeline caching References: <1C1B9824-FD41-11D6-874A-0003935AD2EE@media.demon.co.uk> In-Reply-To: <1C1B9824-FD41-11D6-874A-0003935AD2EE@media.demon.co.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH PLAIN at pop017.verizon.net from [141.156.175.200] at Thu, 21 Nov 2002 07:58:33 -0600 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Jeremy Quinn wrote: > Should internal pipelines, made up of cachable components, be cachable > by CachingCIncludeTransformer? AFAIU: Internal pipeline, when caching implementation is used, will cache its own results in case somebody asks for it again. CachingCIncludeTransformer only purpose is to compose proper key and validity, which should be created using validities of all included parts. PS: Last time I checked, 2.1 caching pipeline implementation was not complete. So, before you file a bug against CachingCIncludeTransformer, check that bug exists in 2.0.4-dev. Vadim > If so, then we have a bug, because they do not seem to cache. > > Thanks for any help. > > regards Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org