Return-Path: Delivered-To: apmail-cocoon-docs-archive@www.apache.org Received: (qmail 25858 invoked from network); 11 Mar 2008 16:18:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Mar 2008 16:18:21 -0000 Received: (qmail 77424 invoked by uid 500); 11 Mar 2008 16:18:18 -0000 Delivered-To: apmail-cocoon-docs-archive@cocoon.apache.org Received: (qmail 77386 invoked by uid 500); 11 Mar 2008 16:18:17 -0000 Mailing-List: contact docs-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: docs@cocoon.apache.org List-Id: Delivered-To: mailing list docs@cocoon.apache.org Received: (qmail 77375 invoked by uid 99); 11 Mar 2008 16:18:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 09:18:17 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.130] (HELO eos.apache.org) (140.211.11.130) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 16:17:49 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id 0D550D2E4 for ; Tue, 11 Mar 2008 16:18:00 +0000 (GMT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: docs@cocoon.apache.org Date: Tue, 11 Mar 2008 16:18:00 -0000 Message-ID: <20080311161800.20579.41380@eos.apache.org> Subject: [Cocoon Wiki] Update of "Caching" by WillSheppard X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cocoon Wiki" for change notification. The following page has been changed by WillSheppard: http://wiki.apache.org/cocoon/Caching ------------------------------------------------------------------------------ ---- === User Questions === - I'd really like to see some information on how to debug caching problems. For instance, if I have a complicated pipeline, is there any way, by looking in the logs, to see which component gave me cached output instead of fresh? + * I'd really like to see some information on how to debug caching problems. For instance, if I have a complicated pipeline, is there any way, by looking in the logs, to see which component gave me cached output instead of fresh? + [[BR]] + * Is the only way to tell which generators are cachable, by looking in the java code? + I see that HttpProxyGenerator does not implement CacheableProcessingComponent. + Do I need to code up a version of HttpProxyGenerator that does implement it in order for it to be cacheable? + - Will +