Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=KHX2/EsuiZ29Oi7eiHOrXCHmQ9R4FmImnsc8Q6A7jUdire1Ve+bYY3W1HXGiZOqxhaKwUBOVb0p5Cu9Y6LBt1SrvI/4bjXDb8aV22DnIUmtkZs3VW75Z2TW5UuiGCJg/bbQV650lXEHgjBHQH3NYHrfE7Itcx2cov4sSeOVl6+k=
  ;
Message-ID: <20061013191604.71830.qmail@web34212.mail.mud.yahoo.com>
Date: Fri, 13 Oct 2006 12:16:03 -0700 (PDT)
From: Elias Ross <generic_elias@yahoo.com>
Reply-To: genman@noderunner.net
Subject: Elias with more concurrency changes -- again
To: log4j-dev@logging.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello again!

Thanks for moving my "concurrent" branch over to the trunk.

I've been working on adding more unit tests, these are attached to bug 24159.
I haven't measured code coverage, but coverage should be pretty decent.

I also worked on a RollingFileAppender implementation. To get this to work, I
found I needed a reentrant locking strategy. I incorporated code from Doug
Lea's concurrent library, which is public domain. If Log4J were to eventually
support Java 1.5, the lock implementation is future replaceable with the JDK
1.5 one.

There still needs to be more heavy load tests, which are hard to write. If
somebody would like to contribute them, that'd be great.

I'd like to see some feedback from the list on these changes. Thanks!


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org