[
https://issues.apache.org/jira/browse/JCS-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762145#comment-15762145
]
Ben Manes commented on JCS-119:
-------------------------------
I don't think so. I know a few Apache projects copied it into their
distribution (e.g. Groovy, Cayenne), shaded (e.g. Camel), or added a dependency
(e.g. Cassandra, OFBiz). Most I discovered after the fact, as I think JCS is
the only that I've proactively prompted wrt CLHM. If there is an electronic
form, I'd prefer that over faxing. None of the Apache projects that switched or
adopted Caffeine have asked, either (Accumulo, et. al.).
My understanding is that the CLA is required for committers. ("A signed ICLA is
required to be on file before an individual is given commit rights to an ASF
project.")
P.S. When (if) you decide to require JDK8, please consider using Caffeine
instead. That would be a dependency or shade, due to the more complex code base.
> replace synchronized blocks by java locks or concurrenhashmap
> -------------------------------------------------------------
>
> Key: JCS-119
> URL: https://issues.apache.org/jira/browse/JCS-119
> Project: Commons JCS
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
> Assignee: Thomas Vandahl
> Fix For: jcs-2.1
>
>
> A cache is typically used in a concurrent environment. Since Java 6 using a
> ReentrantLock is faster than synchronized so can be interesting to replace
> synchronized blocks by a lock.
> Places i'm thinking about:
> * CompositeCache
> * AbstractDoubleLinkedListMemoryCache
> * LHMLRUMemoryCache
> * DoubleLinkedList
> * LRUMap
> * SingleLinkedList
> * SortedPreferentialArray
> Some places where replacing a HashMap by a ConcurrentHashMap can allow to get
> rid of synchronized without needing a lock:
> * CacheEventQueue
> * AbstractDiskCache
> * CacheWatchRepairable
> There are other places but this is the main I saw.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
