I think a well-written FAQ entry or explicit documentation page with recommended solutions would be the most practical solution to alleviating a lot of the pain of the logging conundrum. This page must be easy to find as this situation happens to every user of Restlet, and, well, sucks.
.. Adam On Tue, Apr 8, 2008 at 9:44 AM, Ian Clarke <[EMAIL PROTECTED]> wrote: > It seems ridiculous, I know, but unfortunately if all the existing > options are over-engineered and hard to use, and produce spurious > output in their default configuration, then the natural alternative is > to create a framework that doesn't suffer from these problems. > > Of course, a simple solution to the immediate issue is to ensure that > logging is switched off by default in all code and libraries shipped > with Restlet. > > Ian. > > > > On Tue, Apr 8, 2008 at 11:31 AM, Kevin Conaway <[EMAIL PROTECTED]> wrote: > > So the solution to the confusion surrounding the various log frameworks in > > use by Restlet and its components is....another log framework? :) > > > > As much as I'm against using one of the "bridge" frameworks for logging, it > > might make sense for Restlet seeing as how the various components all could > > (and some indeed do) use different frameworks. > > > > You could also adopt a discovery policy similar to what jetty does > > > > > > > > On Tue, Apr 8, 2008 at 11:17 AM, Ian Clarke <[EMAIL PROTECTED]> wrote: > > > > > Does your colleague have any plans to release his framework under a > > > commercial-friendly license (eg. LGPL)? If so, I'll definitely take a > > > look at it for my own project :-) > > > > > > Ian. > > > > > > > > > > > > > > > On Tue, Apr 8, 2008 at 8:46 AM, Rob Heittman <[EMAIL PROTECTED]> > > wrote: > > > > Heh. One of the guys at my office has been ad-hoc building his own > > personal > > > > logging framework to talk to the logging frameworks. Originally I was > > going > > > > to complain about this on principle, but in truth his code's > > delightfully > > > > easy to read -- simply because his logging classes are intentionally > > simpler > > > > and more ad hoc to the application environment and the information > being > > > > logged. > > > > > > > > Forward a pointer to the blog rant please ;-) > > > > > > > > > > > > > > > > On Tue, Apr 8, 2008 at 9:38 AM, Ian Clarke <[EMAIL PROTECTED]> wrote: > > > > > Personally I blame the design of logging frameworks. I find them to > > > > > be over-engineered, and unintuitive to use. > > > > > > > > > > I hate to say it, but maybe we need a new logging framework :-) > > > > > > > > > > Ian. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Email: [EMAIL PROTECTED] > > > Cell: +1 512 422 3588 > > > Skype: sanity > > > > > > > > > > > -- > > > Email: [EMAIL PROTECTED] > Cell: +1 512 422 3588 > Skype: sanity >
