[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-cocoon-users
Subject:    InputModule output and pipeline caching ?
From:       "Laurent Perez" <hakimm () gmail ! com>
Date:       2006-04-29 23:58:38
Message-ID: 501089280604291658w241f731ao1b1d79a2b1c83e8b () mail ! gmail ! com
[Download RAW message or body]

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="caching" that looks like :

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


[prev in list] [next in list] [prev in thread] [next in thread]