cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Unico Hommes <>
Subject Re: documentation about performance and efficiency and caching
Date Wed, 24 Mar 2004 16:20:45 GMT

You need to write an excalibur Store and configure it in cocoon.xconf. 
See for an example the JCS and EHCache implementations in the scratchpad 
block and the excalibur store package itself.

It's not more than a thin wrapper to adapt your third party solution to 
the contract used in cocoon. This contract is the Store interface and by 
declaring it properly in cocoon.xconf you make it available to other 
components such as the cocoon cache to use it.


Ralph Goers wrote:

>What did you have to do to switch to EHCache?  Assuming it makes sense, I'd
>possibly like to use Tangosol Coherence since we are already using that for
>other purposes.
>-----Original Message-----
>From: Unico Hommes [] 
>Sent: Wednesday, March 24, 2004 4:22 AM
>Subject: Re: documentation about performance and efficiency and caching
>Keep in mind that the caching system is currently in a state of flux 
>given that we are trying to move away from Jisp. A lot of the 
>alternatives manage the paging aspect that now involves the persistent 
>store and store janitors themselves.
>A related observation: I consider the current Jisp version unuseable for 
>any production site. The problem outlined here 
> is very serious 
>and has forced me to use the EHCache store for some of our clients 
>instead (The only useable alternative besides perhaps JCS (haven't tried 
>to use it yet) ATM).

View raw message