[ http://jira.magnolia.info/browse/MAGNOLIA-636?page=all ]

Grégory Joseph updated MAGNOLIA-636:
------------------------------------

    Fix Version/s: 3.1
                       (was: 3.5)

status, feedback, comments ?
how is the current state related to Andreas' patch? Is it derived from it or 
not ?

> Refactored pluggable, manageable cache handling
> -----------------------------------------------
>
>                 Key: MAGNOLIA-636
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-636
>             Project: Magnolia
>          Issue Type: Improvement
>    Affects Versions: 2.1.3
>            Reporter: Andreas Brenk
>         Assigned To: 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://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to