It all sounds good to me as long as API breakage is minimal (or non-existent)
On Wed, Jan 27, 2010 at 1:59 PM, Jeppe Nejsum Madsen <[email protected]>wrote: > Hi, > > I was thinking about some improvements to Lift's logging code: > > 1) Make the slf4j logging configurable in the same way as log4j (ie with > dev, prod logback files) > > 2) Add support for MDC to Lift's logging interface (and the log4j & > slf4j backends) > > 3) Add more logging to Lift :-) > > The last part may be a bit controversial, but I find logging statements > immensely useful when trying to diagnose stuff that doesn't work or > figure out how stuff works. If separate loggers are created for > different areas (i.e mapper, comet, ajax, etc) it should be possible to > turn the needed info on & off without too much information overload. > > Performance wise it shouldn't matter much (famous last words :-) if > logging is disabled. > > Thoughts? > > /Jeppe > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
