Hey,
What do you guys think about overhauling the caching layer to be compliant
with the upcoming Jcache api? (jsr-107)
In specific, I've been experimenting some with ehcache
(http://ehcache.sourceforge.net/ , Apache OS license) and it seems to be a
very comprehensive implementation, as well as fully compliant with the API. 
I think the benefits are numerous: in respect to ehcache itself, it seems to
be a very mature implementation, supporting most classical cache schemes as
well as some interesting distributed cache options (and of course,
performance-wise its very lucrative in terms of reported multi-cpu scaling
performance and  some of the benchmark figures they show). 

Further, abstracting away the caches to use the jcache api would probably
make it easier in the future to make the whole caching layer more easily
swappable with some other implementations that will probably crop up.

Maybe for the 1.5 roadmap? just a thought...

Chak

-- 
View this message in context: 
http://www.nabble.com/JCache-API-and-EHCache-tp22667097p22667097.html
Sent from the Solr - Dev mailing list archive at Nabble.com.

Reply via email to