cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Froehlich" <>
Subject FYI: simplestore discussion on jakarta-commons
Date Fri, 18 Jan 2002 08:31:11 GMT
simplestore is based on our Store implementation. This wrote Juozas on that
issue and I would like to have your opinouns on that. I was -well- a little
bit shocked and therefore not very objectiv.


simplestore is not the best optimization for projects like Cocoon.
You don't need it here. You don't need JISP and  StoreJanitor.
It kind of abstraction, but forget it if you need performance and want to
save resources.
There are a lot of better ways to solve this problem.

1. Intercept request for HTTP Headers "Send IF Not Modified".
  You can cache some content on client side.
2. Don't use single file for cache. Map URL to file and store "large"
content in file OS will do all this MRU stuf and cache for file system.
3. Don't write content to file if it is "small" store it in memory,
  you will have statistics on next request, and here you can decide what
"large", "small","old","new","fast","slow".
4. Don't use any background cleanup, delegate all resource  management
stuff for OS,JVM,GC where possible.

I don't know Cocoons code, it is possible there are more solutions and
believe you will find them.

I believe we will make simplestore to be a good and abstact, but it is not
solution for all cases, it can become
too "abstact" and it will be not "simple". It too simple for store and too
complex for optimizations.
You can forward my emails for Cocoon developers, I believe they will
understand me and this will help for you.
Cocoon seems very good framework for me, but I am not going to use it in
any of my projects at this time, there are a lot of work to do.

To unsubscribe, e-mail:
For additional commands, email:

View raw message