I'm working on a project where I'm implementing a 3rd party
proprietary/(mostly undocumented) network protocol.
One of my logging statements dumps each byte as it's received/sent over the
network. This is used in the "direst" debugging situations, and can
obviously generate a very large number of
My boss is away, so I'm taking the opportuinity to clean up my code. I have
a set of standards I use for style, formatting, documentation, naming etc.
I also have a set of coding idioms I like to follow (Law of Demeter, code
metric limits, etc).
My problem is I don't yet have a set of logging idi
> I'm still puzzled by why you want to do this. If stdout and stderr are
both
> just writing to the screen, why differentiate them? And if one is being
> redirected to a file, why not use a file appender?
"just writing to the screen" is not quite the way to think of it.
There's a reasong it's
Better question:
Why have any level's implemented?
Probably because it's useful to have sensible default implementations.
"TRACE" or "FINE" is one that many seem to agree is sensible and required.
I think the idea is, no matter how many or few default levels there are,
the defaults should cover
