Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 57755 invoked from network); 2 Nov 2008 15:11:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Nov 2008 15:11:36 -0000 Received: (qmail 48651 invoked by uid 500); 2 Nov 2008 15:11:41 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 48571 invoked by uid 500); 2 Nov 2008 15:11:41 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 48560 invoked by uid 99); 2 Nov 2008 15:11:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Nov 2008 07:11:41 -0800 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.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Nov 2008 15:10:33 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 402A7234C23E for ; Sun, 2 Nov 2008 07:10:44 -0800 (PST) Message-ID: <1378734656.1225638644247.JavaMail.jira@brutus> Date: Sun, 2 Nov 2008 07:10:44 -0800 (PST) From: "Steven Dolg (JIRA)" To: dev@cocoon.apache.org Subject: [jira] Updated: (COCOON3-9) Generalize the PipelineCache, so that it can be used as a general purpose cache for PipelineComponents as well. In-Reply-To: <1916827904.1225634624680.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/COCOON3-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Dolg updated COCOON3-9: ------------------------------ Description: Currently the PipelineCache is very specific for caching the complete results of a pipeline execution. COCOON3-6 is the first issue requiring a caching mechanism at the PipelineComponent level. With only some minor modifications the PipelineCache can be used for those requirements. was: Currently the PipelineCache is very specific for caching the complete results of a pipeline execution. COCCON3-6 is the first issue requiring a caching mechanism at the PipelineComponent level. With only some minor modifications the PipelineCache can be used for those requirements. > Generalize the PipelineCache, so that it can be used as a general purpose cache for PipelineComponents as well. > --------------------------------------------------------------------------------------------------------------- > > Key: COCOON3-9 > URL: https://issues.apache.org/jira/browse/COCOON3-9 > Project: Cocoon 3 > Issue Type: Improvement > Components: cocoon-pipeline > Affects Versions: 3.0.0-alpha-1 > Reporter: Steven Dolg > Assignee: Cocoon Developers Team > Fix For: 3.0.0-alpha-2 > > Attachments: cache.patch > > > Currently the PipelineCache is very specific for caching the complete results of a pipeline execution. > COCOON3-6 is the first issue requiring a caching mechanism at the PipelineComponent level. > With only some minor modifications the PipelineCache can be used for those requirements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.