One of the big design decisions left for pool2 is whether or not to add logging. If logging is added then that opens up the what to log and with which logging framework questions.
I do think some form of logging is required. See POOL-131 for one example of where logging could be useful. I have a preference for commons-logging. Partly since it is eating our own dog food, partly because it will make updating Tomcat to use pool2 easier. I did have a random thought that we could do zero logging but emit JMX notifications if JMX was enabled. It avoids the "which framework" debate but uses an approach that is far less widely used in my experience. All this is because I am (hopefully) getting close to the point where the pool2 code is ready for an alpha release. Thoughts? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
