Changes between Version 18 and Version 19 of MapGuideRfc49

Timestamp:

06/16/08 13:43:55 (17 years ago)

Author:

trevorwekel

Comment:

--

MapGuideRfc49

@@ -58 +58 @@
   * Traces with parameters are logged for internal API calls
 
-The current thread identifier will be added to both the error and trace logs.  This information is useful for call stack tracing.  STACKTRACE support also will be added to the trace log for warning and error messages.
+In the absence of a !LogsDetail entry in serverconfig.ini, each service will default to level 0.  By default !LogsDetail = "" so all services will default to level 0.  
 
-The existing Error log will be enhanced to include warning messages for a service and call parameters, if desired.
+In addition to the new classification scheme, the following improvements/changes will be made to the logging:
+ * The current thread identifier will be added to both the error and trace logs.  This information is useful for call stack tracing.
+ * STACKTRACE support also will be added to the trace log for warning and error messages.
+ * The existing error log will be enhanced to include warning messages for a service and call parameters, if desired.
+ * The existing trace log will also include error messages, warning messages and call parameters, if desired.  Each operation will have two entries tagged with BGN and END for timing purposes.
+
+Here is a sample error log:
 
 {{{
@@ -81 +87 @@
 }}}
 
-The existing Trace log will also include error messages, warning messages and call parameters, if desired.  Each operation will have two entries tagged with BGN and END for timing purposes.
+Here is a sample trace log:
 
 {{{