cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leszek Gawron <lgaw...@mobilebox.pl>
Subject Re: Caching jx *without* flow
Date Mon, 18 Sep 2006 08:09:38 GMT
Thorsten Scherler wrote:
>> <map:match pattern="foo">
>>    <map:generate src="foobar.jx">
> 
> that is the normal file generator which is indeed cacheable. I am
> talking about <map:generate type="jx" src="foobar.jx"> which is not
> cacheable (if not changed since the last update of the cocoon in
> forrest).
I am sorry - it should of course state <map:generate type="jx" 
src="foobar.jx">

JXTG IS cacheable if you provide jx:cache-key and jx:cache-validity in 
template body.

>>      <map:parameter name="foo" value="bar"/>
>>      <map:parameter name="bar" value="foo"/>
>>    </map:generate>
>>    <map:serialize/>
>> </map:match>
>>
>> so cocoon:/foo gets cached with something like "foo=bar&bar=foo"?
>>
>> Why need a patch for that? After all you already have jx:cache-key and 
>> jx:cache-validity.
> 
> Can you explain, I read the mail from Ard (see above marc link) and
> understood that one need to patch the jx generator to make it cacheable.
> If not can you give an example?

Please read my other reply. If I have time I will commit some samples to 
trunk that would outline jxtg caching.

-- 
Leszek Gawron, IT Manager                          MobileBox sp. z o.o.
+48 (61) 855 06 67                              http://www.mobilebox.pl
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65

Mime
View raw message