cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hochsteger Andreas /INFO-MA <>
Subject RE: [RT] rethinking the cache storage system
Date Mon, 23 Feb 2004 15:59:04 GMT
Wouldn't it then be possible to serve valid content directly from the apache
webserver by using the cache on the disk?
You get the best performance boost, if you don't have to bother cocoon at
But I think the problem is: How does Apache know, if the content is still
valid? :-(
Perhaps it would be only a solution for dynamically generated binary files
(images, pdfs, ...) where you know beforehand that they are valid for a
certain time.


> -----Original Message-----
> From: Stefano Mazzocchi []
> Sent: Monday, February 23, 2004 4:47 PM
> To: Apache Cocoon
> Subject: [RT] rethinking the cache storage system
> We were using Jisp and Scott's decision makes it clear that we either:
>   - have to maintain Jisp 2.x ourselves
> or
>   - use something else
> Here I would like to ask you a much easier question: do we 
> really need 
> it? can't we just our storage into a bunch directories and 
> use that as a 
> file system? that works very well for file-intensive setups like mail 
> client/servers and browser caches, why shouldn't it work for us?
> My gut feelins is that having such a critical piece of our 
> infrastructure so away from the metal is actually hurting us, both 
> performance and complexity wise.
> I would love to use BerkeleyDB, but it's native, incompatibly 
> licensed 
> and has terrible Java APIs. And all the problems of binary 
> stores: you 
> can't see inside from your shell!
> I think that a better use of the file system would yield much more 
> performance, since JVM IO is pretty much optimized for file access 
> anyway (and uses OS-level caching).
> thoughts?
> -- 
> Stefano.
> Wurde auf Viren ueberprueft !!!

View raw message