Message20465
Logged In: YES
user_id=3066
Looking at this again, after adjusting the application I
have that used the connection-specific loggers, I decided
that a different approach better solves the problem.
What you've shown requires exactly what I wanted to avoid:
having to make a gesture at each logging call (to transform
the message). Instead of doing this, I ended up writing a
wrapper for the logger objects that implement the methods
log(), debug(), info(), warn(), warning(), error(),
exception(), critical(), and fatal(). These methods each
transform the message before calling the underlying logger.
It would be really nice to have something like this that
isolates the final call to Logger._log() so specific
implementations can simply override _log() (or some other
helper routine that gets all the info) and maybe the
__init__(). I don't think that's completely necessary, but
would probably make it a lot easier to implement this pattern.
There's probably some useful documentation improvements that
could be made to help people avoid the issue of leaking loggers. |
|
Date |
User |
Action |
Args |
2007-08-23 14:20:52 | admin | link | issue932563 messages |
2007-08-23 14:20:52 | admin | create | |
|