Return-Path: 
 <users-return-86526-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: (qmail 73201 invoked from network); 29 Apr 2006 23:59:16 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 29 Apr 2006 23:59:16 -0000
Received: (qmail 82353 invoked by uid 500); 29 Apr 2006 23:59:09 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 82278 invoked by uid 500); 29 Apr 2006 23:59:09 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
List-Post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
List-Id: <users.cocoon.apache.org>
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 82266 invoked by uid 99); 29 Apr 2006 23:59:09 -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 16:59:09 -0700
X-ASF-Spam-Status: No, hits=1.3 required=10.0
	tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of hakimm@gmail.com designates
 64.233.184.233 as permitted sender)
Received: from [64.233.184.233] (HELO wproxy.gmail.com) (64.233.184.233)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Apr 2006 16:59:08 -0700
Received: by wproxy.gmail.com with SMTP id i31so1875481wra
        for <users@cocoon.apache.org>; Sat, 29 Apr 2006 16:58:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=C5gB45UpRpJC4OdyQuuEj5WYkpifh2uiITsGwCMQ3PYMbCnOyPo3iS+syXO09IvyxsTHHdQux2qR8yIFepA9KysJpbVv0g1EHeGnd4lA5mv/FFqWUB9mylmzU827LWYBC1/YVesf9gahV9wLqw6OTTIs7tkU5FxA51ha9wfVf5I=
Received: by 10.65.241.1 with SMTP id t1mr1390183qbr;
        Sat, 29 Apr 2006 16:58:38 -0700 (PDT)
Received: by 10.65.54.6 with HTTP; Sat, 29 Apr 2006 16:58:38 -0700 (PDT)
Message-ID: <501089280604291658w241f731ao1b1d79a2b1c83e8b@mail.gmail.com>
Date: Sun, 30 Apr 2006 01:58:38 +0200
From: "Laurent Perez" <hakimm@gmail.com>
To: users@cocoon.apache.org
Subject: InputModule output and pipeline caching ?
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hello

AFAIK, Cocoon caching mechanism tries to cache a pipeline processing
workflow "until it meets a non-cacheable element" (correct me if I'm
mistaken :)).

My question is rather simple, given the above hopefully correct
assumption. If I have a pipeline with type=3D"caching" that looks like :

<map:match pattern=3D"foo">
<map:aggregate element=3D"root">
<!-- various map:part reading xml flat files on disk which are
sometimes updated -->
</map:aggregate>
<map:transform src=3D"{myinputmodule:someproperty}/foo.xslt"/>
<map:serialize type=3D"xml"/>
</map:match>

and given that the someproperty output value is dynamic, because based
on dynamic request parameters the myinputmodule uses to alter that
property :

will Cocoon cache the first inputmodule return value, and use it until
the cache has to be refreshed, or will it *instead* cache each and
every inputmodule value returned ?

in other words, will I end up with one cached xslt transformation
bound to the first inputmodule value ever returned, or with multiple
cached transformations, because Cocoon is "smart enough" to understand
the transformer part uses a dynamic source, knowing that the {} might
return different values ?

thanks
laurent


--
<a href=3D"http://in-pocket.blogspot.com">http://in-pocket.blogspot.com
- Mobile world, technology and more</a>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org