Brian Holmes wrote:
>4.2 Support more verbose output and debug tracing.
>
>I don't think this requires much explanation.
>
No, but it requires a strong objection.
>Developers and users
>alike could get a lot of help from tracing and verbose logging. It's
>been requested several times on the mailing list. I'm sure if the
>functions were there today many people would start using them.
>
>
Please do not confuse "verbose logging" and "debug tracing". Logging and
debug tracing are conceptually different and imho should not be
implemented in the same way.
Logging provides a record of the operations performed by the applicatio
(e.g., requests served), as an input for audits and security analysis.
It's turned on by default, typically cannot be turned off completely,
allows only minimal choice of verbosity and output configuration (e.g.,
songle log file vs. separate noremal/error log, etc.), and does not
significantly affect application performance even in the most verbose
configuration.
Debug tracing is a tool intended to help developers to diagnose
problems. It's turned off by default, provides lots of different knobs
for controlling the amount, verbosity and source of the trace data, and
is allowed to slow application performance to a crawl if a really
detailed trace is required. Typically that means that tracing is even
implemented differently than logging.
I've seen logging and debug tracing being discussed in the same breath
(and implemented as if they were the same thing) so often that it hurts.
I don't want this to happen in Subversion.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 13 03:28:20 2005