http://bugzilla.slf4j.org/show_bug.cgi?id=49
Summary: Add MDC (mapped diagnostic context) to SLF4J
Product: SLF4J
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P4
Component: Core API
AssignedTo: dev@slf4j.org
ReportedBy: [EMAIL PROTECTED]
I really like SLF4J: it's the best logging interface out there and provides an
excellent, sound solution to the problem of logging for embedded libraries.
I've been transitioning most of my applications to SLF4J and LOGBack where
possible.
I would like to propose that you consider moving the MDC interface from LOGBack
and the log4j bridge to SLF4J. To me, this is general logging functionality
from which a library can benefit without assuming it'll write to Log4j or
LOGBack. An implementation that doesn't support diagnostic contexts could just
ignore the capability.
In my position, I write lots of code that's of general utility for the rest of
our business. SLF4J has been great for this, but I do sometimes find that
diagnostic contexts would be appropriate. Especially annoying is that the only
way I can do this in a relatively compatible way is to use the log4j interface
and the bridge for LOGBack applications. Things would be much simpler for me,
and I'd get better use out of diagnostic contexts, if this were a part of
SLF4J.
--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
