Hi Chris,
Thank you for the detailed review, this really helps - appreciate it
very much.
I do agree with your concerns on memory leaks and the difficulty of
dealing with that in the absence of a pool.
And improvements you have suggested makes quite sense.
However I need more time
Eran Chinthaka wrote:
Keeping how log4j behaves in mind, shouldn't this be configurable?
Ishan prefers to see it like [] [] []
[], but others might not. I assume there is a logging
conf file some where.
We dont have a logging conf file - sounds like it is a good idea to have
one.
However, we
There is Log4C
Don't know how mature it is but it is based on the Log4j and seems to
have a generally accepted model for configuration.
On 04/11/2006, at 8:25 PM, Samisa Abeysinghe wrote:
Eran Chinthaka wrote:
Keeping how log4j behaves in mind, shouldn't this be configurable?
Ishan prefe
Samisa Abeysinghe <[EMAIL PROTECTED]> writes:
> We have been always releasing voting on the plan. Can you lead to any
> pointers that suggest otherwise in apache please?
http://www.apache.org/foundation/voting.html
Describe a point about release voting.
Votes on whether a package is ready to be
