FYI I attached a patch using a ConcurrentHashMap here https://issues.apache.org/jira/browse/JCS-127
It is pretty fast compared to previous impl. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-06 8:31 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>: > Hi guys, > > few questions about jcs: > > 1) I played a bit with remote cache server etc and didn't find a lot > of use cases, do we keep it this way (linked to 4) )? > 2) API: do we use JCache as main API or do we keep core? > 3) Reviewing JCache module I really wonder if we shouldn't use a > ConcurrentHashMap instead of a the currently backing CompositeCache > and add on top of this "locally optimized" implementation two things: > a) eviction (a thread regularly iterating over local items to check > expiry would be enough), b) distribution (see 4) ) > 4) distributed mode: I wonder if we shouldn't rethink it and > potentially add Cache<K, V> listeners usable in JCache to know if > another node did something (useful to get consistent stats at least - > basically we need a way to aggregate on each note stats) + use a key > for each node to keep data on a single node + potentially add backup > on another node. > > wdyt? > > I don't know how much JCS is used ATM and if we can break that much > the API but since that would be a 2.0 I think it is the moment > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
