> > I have noticed that even with logging set to normal with verbosity set > to 1 we now seem to get quite a bit of logging information - >
I've been using log4j from IBM and it seems pretty cool. It has niceties like rolling logfiles, logging to a socket, and logging to syslogd built in, and the jar is only about 40K. It also lets you massively reconfigure your log settings without recompiling. Here's a big scary URL that should work: http://alphaworks.ibm.com/aw.nsf/frame?ReadForm&/aw.nsf/techmain/3005162 DEE6218E08825680B000455FC I have a related problem: I'd like to reuse the RequestClient, but it's talking to the Logger directly via static methods and I find that unacceptable. I'd like more control over logging in the context of a larger app, which means using objects instead of static functions. If no one minds, I'd like to wrap the Logger calls in RequestClient and InsertClient with some kind of interface (that defaults to a Logger-based impl) so I can reuse those classes. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
