[ http://jira.magnolia.info/browse/MAGNOLIA-636?page=comments#action_11762 ]
Fabrizio Giustina commented on MAGNOLIA-636: -------------------------------------------- done: - add jmx dependency (needed to compile on jdk 1.4) - implement the module interface and remove dependencies from config - move the code to the appropriate module - change logging code from log4j to slf4j - make it work without requiring a configured domain (more or less) the new cache module is almost complete, but at the moment it doesn't work due to the changes in authentication in svn trunk. What I would like to do is removing the need for a separate thread/request at all, and simply caching the result of the CURRENT request by gathering the response result from the filter. This makes everything simpler and reduce the number of requests that need to be handled by Magnolia... the new thread management stuff could beremoved by choosing this path. If I remember well OSCache has a similar working http filter. Thoughts? > Refactored pluggable, manageable cache handling > ----------------------------------------------- > > Key: MAGNOLIA-636 > URL: http://jira.magnolia.info/browse/MAGNOLIA-636 > Project: magnolia > Type: Improvement > Versions: 2.1.3 > Reporter: Andreas Brenk > Assignee: Fabrizio Giustina > Priority: Minor > Fix For: 3.1 > Attachments: cache.patch, cache.tar.gz, config.server.cache.xml > > > I've refactored the CacheHandler to use a pluggable implementation. One being > the existing filesystem based one and another ehcache-based. It optionally > keeps statistics about cache hits and misses is JMX manageable. It's also > completely configurable using the existing cache config node in the > repository. Cache thread usage is configurable using the util.concurrent > Executors (one Thread for each request as it is now or a ThreadPool, or a > single Thread, ...). The ehcache implementation has configurable memory and > disk cache size and lifetime parameters and can use sophisticated expirations > strategies like "first in first out" or "least recently used". > The code is currently for Magnolia 2.1.3. > What is the best way to get this integrated? And what is the interest? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
