Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 84390 invoked from network); 29 Apr 2006 18:33:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Apr 2006 18:33:03 -0000 Received: (qmail 94695 invoked by uid 500); 29 Apr 2006 18:33:00 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 94250 invoked by uid 500); 29 Apr 2006 18:32:58 -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 94239 invoked by uid 99); 29 Apr 2006 18:32:58 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Apr 2006 11:32:58 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of NilsKaiser@gmx.net designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 29 Apr 2006 11:32:57 -0700 Received: (qmail invoked by alias); 29 Apr 2006 18:32:36 -0000 Received: from e178068162.adsl.alicedsl.de (EHLO [10.0.0.11]) [85.178.68.162] by mail.gmx.net (mp019) with SMTP; 29 Apr 2006 20:32:36 +0200 X-Authenticated: #32721211 Message-ID: <4453B13C.90005@gmx.net> Date: Sat, 29 Apr 2006 20:32:28 +0200 From: Nils Kaiser User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Custom Pipeline Caching Content-Type: multipart/alternative; boundary="------------060907070207060906040706" X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --------------060907070207060906040706 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hello, I have a complex pipeline which contains some self written components that generate and transform data in steps that cannot really be cached (dependent on external resources like the result of a request...). What are the possibilities to implement a custom cachin scheme? Is there a way to define a step in the pipeline where caching is possible again (not just if all preceding components are cache-aware?). Greetings, Nils --------------060907070207060906040706 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Hello,

I have a complex pipeline which contains some self written components that generate and transform data in steps that cannot really be cached (dependent on external resources like the result of a request...).

What are the possibilities to implement a custom cachin scheme? Is there a way to define a step in the pipeline where caching is possible again (not just if all preceding components are cache-aware?).

Greetings,

Nils
 --------------060907070207060906040706--