Ugo Cei wrote:
Vadim Gritsenko wrote:
Why then we need EHCache at all? MRUMemoryStore works well and does not require extra jar files. What EHCache gives us?
Overflowing to disk when the memory store fills, all with a single implementation.
Please re-read email. You omitted a quote:
3) Configure EHCache with a ZERO-sized disk store.
Now, assuming above, what does it give us?
Overflowing to disk when the memory store fills, all with a single
implementation, IF you configure the disk store with a greater-than-zero size, which requires changing a parameter in cocoon.xconf, since - as shipped - it defaults to "memory only".
Hope it is clearer, now :-).
Ugo
