hi bart, On Wed, Feb 17, 2010 at 11:29 PM, Bart van der Schans <b.vandersch...@onehippo.com> wrote: > Hi, > > Right now there are several "homegrown" caches in Jackrabbit. Some > configurable, some based on soft/weak references. Using JCache it > would make it possible to leverage existing caching implementations.
jcache and friends have been suggested a number of times before. i had a look at jcache, ecache etc quite while ago, they didn't fit the the needs of jackrabbit core. the 'homegrown' caches in the core are not simple caches (holding serializable objects), the have special semantics and are fundamental to jackrabbit's implementation of isolation levels. none of the caching framworks i looked at supported the required semantics. general purpose caching frameworks are probably fine at an application level, at the core level i'd rather rely on custom implementations that exactly do what we need, nothing more and nothing less. the core should IMO be small and higly optimized, not bloated with general purpose frameworks/black boxes ;) cheers stefan > This could help in making the caches better configurable and tunable > and have features like overflow to disk, which could help with large > transactions, persist caches to disk during restart for cache warming > and clustered caches. For example it could be interesting to share > bundle/item state caches between cluster nodes. > > Regards, > Bart >
