PING
On 29 May 2014 03:00, sebb seb...@gmail.com wrote:
On 28 May 2014 18:06, rmannibu...@apache.org wrote:
Author: rmannibucau
Date: Wed May 28 17:06:12 2014
New Revision: 1598071
URL: http://svn.apache.org/r1598071
Log:
using reentrant locks instead of old synchronized
-1
This
On 1 June 2014 18:54, Romain Manni-Bucau rmannibu...@gmail.com wrote:
2014-06-01 19:45 GMT+02:00 sebb seb...@gmail.com:
PING
Pong, sorry, missed this one.
On 29 May 2014 03:00, sebb seb...@gmail.com wrote:
On 28 May 2014 18:06, rmannibu...@apache.org wrote:
Author: rmannibucau
well it is for sure thread safe. Not sure I get why final and synch would
be mandatory in this particular case (field will maybe be cached by thread
but that's not an issue since the value will be unique).
I have nothing against a revert/reapply. I'll open a thread on logging btw.
Romain
Hi
I have two main point to discuss regarding the logging:
1) LogHelper stuffI committed. Idea was to cache isDebugEnabled to get a if
(boolean) complexity and not go through the logging framework which can
imply several layers (filter, appender, handler, logger...) for nothing and
slow down
I have gone through Wikipedia and R functions to get an understanding.
My idea is to come up with different estimation techniques as strategies
(Enums) and constrction inject during percentile object creation.
The evaluate method could then use this estimation tecnhique to complete
the
On 1 June 2014 20:19, Romain Manni-Bucau rmannibu...@gmail.com wrote:
well it is for sure thread safe. Not sure I get why final and synch would be
mandatory in this particular case (field will maybe be cached by thread but
that's not an issue since the value will be unique).
non-final fields
On 1 June 2014 20:26, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Hi
I have two main point to discuss regarding the logging:
1) LogHelper stuffI committed. Idea was to cache isDebugEnabled to get a if
(boolean) complexity and not go through the logging framework which can
imply several
There is also log4j 2.
Gary
div Original message /divdivFrom: Romain Manni-Bucau
rmannibu...@gmail.com /divdivDate:06/01/2014 15:26 (GMT-05:00)
/divdivTo: Commons Developers List dev@commons.apache.org
/divdivSubject: [jcs] logging /divdiv
/divHi
I have two main point to
Hi!
Congratulations on your BeanUtils 1.9.2 release.
There is a trivial copy-pasted typo in the release notes file: the
title for 1.9.1 changes on line 66 says 1.9.0.
I think it is not worth creating a JIRA issue for this.
[[[
Index: RELEASE-NOTES.txt
Am Sun, 1 Jun 2014 23:43:10 +0100
schrieb sebb seb...@gmail.com:
On 1 June 2014 20:19, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
well it is for sure thread safe. Not sure I get why final and synch
would be mandatory in this particular case (field will maybe be
cached by thread but
Well ATM log4j2 doesnt work well, didnt get time to dig into it but tested
last week for another topic and lost all my shutdown messages (guess
cleanup is called too early).
3 would be an option if we dont rely on [logging] anymore but the impl
directly which would be a regression IMHO + either
Le 02/06/2014 02:36, Konstantin Kolinko a écrit :
There is a trivial copy-pasted typo in the release notes file: the
title for 1.9.1 changes on line 66 says 1.9.0.
Fixed, thank you Konstantin.
Emmanuel Bourg
-
To
12 matches
Mail list logo
