[seam-dev] Page fragment cache with JBoss Treecache, ehcache and a FileSystemCache

Pete Muir pmuir at bleepbleep.org.uk
Sat May 3 06:31:54 EDT 2008


On 3 May 2008, at 11:19, Sebastian Hennebrueder wrote:

> Christian Bauer schrieb:
>>
>> On May 03, 2008, at 11:48 , Pete Muir wrote:
>>>> FileSystemCache
>>>> Manually written, idea: a large site cannot be hold in a cache  
>>>> being present in memory. This cache has a small in memory area  
>>>> holding very frequent files (size can be configured) and fetches  
>>>> files from disk.
>>>> Though the operation system caches access to disk, this is still  
>>>> a lot slower than memory access but probably faster than having  
>>>> complex queries to the database (see Seam Wiki queries)
>>>
>>> I'm not quite sure why we need this?
>>
>> Given that ehcache supports configurable overflow to disk, I  
>> concur._______________________________________________
>
> I will test the behaviour of EHCache using the Disk Overflow and  
> give you a feedback on this.
>
>
>
> JBoss Cache 1.x and 2
> This won't be compilable at the same time.

Yup. But JBoss 4 uses 1, and JBoss 5 uses 2. And from my  
experimentation you can't use 1 in JBoss 5 or 2 in JBoss 4.

> How shall I provide this, because I would break the build.

Dunno ;-) Thats part of the challenge. However we definitely need to  
support both.

> I will provide the abstraction for the Pojo as well, though I do not  
> perfectly see the need. It is slower than the normal JBoss Cache  
> (alias TreeCache).

Because we already support it?

>
>
> Best Regards
>
> Sebastian
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev




More information about the seam-dev mailing list