MS RFC 28: Redesign of LOG/DEBUG output mechanisms

[Tamas Szekeres]

Daniel,

As far as I can understand you propose to keep a global variable that
will be set in msSetup() (if the environment variable is set) and
might be modified when each mapfile is parsed. How this implementation
would work in a multithreaded environment? For example when handling
one request would open  /tmp/mapserver1.log while another would use
/tmp/mapserver2.log.
In addition I wonder how the open file handles are reusable by
multiple threads in the various environments.

It would be pretty useful to support the Windows OutputDebugString API
as well. That would make the life of the Windows developers much
easier and establish the ability to use external programs like
SysInternals debugview to display the debug output. (I think there
have been some  issues in the -users list in this question before) For
using this function <windows.h> should be included which have already
included in many places in the code.

Best regards,

Tamas



2007/6/15, Daniel Morissette <dmorissette at mapgears.com>:
> Hi Dev's,
>
> I have prepared a first version of MS RFC 28 that proposes a cleanup of
> the LOG/DEBUG output mechanisms while keeping things simple (I like
> simple) and not breaking too much existing code:
>    http://mapserver.gis.umn.edu/development/rfc/ms-rfc-28
>
> Comments welcome... and expect two more RFCs from me today...
>
> Daniel
> --
> Daniel Morissette
> http://www.mapgears.com/
>