From users-return-99234-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org Wed Apr 20 16:08:17 2011 Return-Path: X-Original-To: apmail-cocoon-users-archive@www.apache.org Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D3B221B6E for ; Wed, 20 Apr 2011 16:08:17 +0000 (UTC) Received: (qmail 79285 invoked by uid 500); 20 Apr 2011 16:08:17 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 79226 invoked by uid 500); 20 Apr 2011 16:08:17 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 79170 invoked by uid 99); 20 Apr 2011 16:08:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2011 16:08:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of scherler@gmail.com designates 74.125.82.179 as permitted sender) Received: from [74.125.82.179] (HELO mail-wy0-f179.google.com) (74.125.82.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2011 16:08:09 +0000 Received: by wyg36 with SMTP id 36so950115wyg.24 for ; Wed, 20 Apr 2011 09:07:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=YzkmZIwFFaKVRrC6VAaH+ERKHKJq8R0ItA0HHzf3+DU=; b=uSmEVQIsnB4rkHxHlOspQmEGwdYmjGNqZHINs2Ujhb1eJJEIsMh4jmNQ9VWHRp9GBg UQ95jLuxqLzFxR6lMHpNetbFTOT1H7aT+ataoZ5NwFWLxMmFrua3L+VyKhDzV9ixa18z HNGSRG8yULkA3tagvBhzo2VAxXbyLhw7qqmQU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=KbI6znL1R8PE88cmgSN8M5znkMFEuJlz6pA8pZsolj8l9ldq9hQJNeslhkaCGQY1GO S9+CTj8Yp4iahoFiHUIQHbAX8vY1+faoKJd4rXGkZ0vxSXcg7+FwrlqpIfaxgJhnPrR8 f1eJ/sfTcIowVDjoAlNRcCs7lYK2SbraULTNo= Received: by 10.227.108.105 with SMTP id e41mr7957599wbp.48.1303315668852; Wed, 20 Apr 2011 09:07:48 -0700 (PDT) Received: from [192.168.1.33] (70.Red-88-11-38.dynamicIP.rima-tde.net [88.11.38.70]) by mx.google.com with ESMTPS id h11sm663540wbc.9.2011.04.20.09.07.46 (version=SSLv3 cipher=OTHER); Wed, 20 Apr 2011 09:07:47 -0700 (PDT) Subject: Re: Cocoon caching with multiple pipelines From: Thorsten Scherler To: users@cocoon.apache.org In-Reply-To: <1302778979.2182.142.camel@DLIB-ROBIN> References: <1302778979.2182.142.camel@DLIB-ROBIN> Content-Type: text/plain; charset="UTF-8" Date: Wed, 20 Apr 2011 18:07:40 +0200 Message-ID: <1303315660.19631.24.camel@mcKenny> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Robin, http://cocoon.apache.org/2.1/userdocs/concepts/caching.html "The default algorithm uses a very easy but effective approach to cache a request: The pipeline process is cached up to the most possible point." In your case if your second pipeline is based on a non caching generator/transformer the complete pipeline is not cacheable. Since the validity has changed the pipeline as a whole is not cacheable. salu2 On Thu, 2011-04-14 at 12:02 +0100, Robin Taylor wrote: > Hi, > > I am a newbie to this list so please forgive me if my question betrays > an ignorance of Cocoon. I am trying to understand a caching problem I am > encountering. > > I have 2 pipelines each made up of cacheable components. Cocoon spots > that the SourceValidity object for a Transformer in the first pipeline > has changed and so regenerates the output from that point onwards in the > pipeline. The second pipeline uses the output from the first pipeline as > its input, does the second pipeline know that the first pipeline > regenerated its output ? Is it possible that Cocoon could reuse the > cached output from the first component in the second pipeline (a > Transformer) rather than run the Transformer using the regenerated > input ? > > Cheers, Robin Taylor. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org > For additional commands, e-mail: users-help@cocoon.apache.org > -- Thorsten Scherler codeBusters S.L. - web based systems http://www.codebusters.es/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org