the point is putIfAbsent is costly but globally once (can be done
concurrently but this is ignorable at runtime). Only important thing is to
ensure then the system uses a single instance.
Issue with sychronized is that it doesn't scale. If you go upper to 10
threads you are slow.
The other point
Globally agree
Next question is: do we plan a 2.0.0-alpha without it (said otherwise I'd
like JCache to be out ASAP and avoid what we live @BVal taking soon 1 year
to release) or do we wait to be very stable to do a proper 2.0.0?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau
Hello,
I think it is usefull to have an Interface which allows
non-serializeable Keys and Values. First of all this is usefull for
actual in-heap implementations (and a generic Map replacement) but
also for a modular approach where you can plug-in custom serializers.
In fact I would consider this
This is a vote to release Commons BeanUtils 1.9.2 based on the first RC.
There was a fix related to a security issue which should now be made
available.
BeanUtils 1.9.2 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/beanutils/ (svn
revision 5419)
Maven arti
On 25.05.14 17:45, Phil Steitz wrote:
> On 5/25/14, 8:18 AM, Romain Manni-Bucau wrote:
>>> And please consider reacting to Phils comment on the removal of
>>> synchronized keywords. It took years to pinpoint the race issues in the
>>> JCS code. I don't claim the current situation to be perfect but
On 25.05.14 17:18, Romain Manni-Bucau wrote:
> Extras is a set of useful basic classes for JCache usage. OpenJPA is JCache
> support for L2 cache in openjpa.
>
> The goal is to make what we propose with jcache module as usable as
> possible and avoid glue code as much as possible in application co
