When trace logging is enabled, the file is opened, appended to and
closed for each socket function call. This makes it possible for an
application to append its own logging information, however care
should be taken to ensure that the file is closed before the next
network operation is performed. To limit the size of the log files,
enable and disable logging only around those sections of code that
you wish to trace.
Note that the TRACE_HEXDUMP trace level generates very large log
files since it includes all of the data exchanged between your
application and the server.
Trace method logging is managed on a per-thread basis, not for
each client handle. This means that all SocketTools libraries and
components share the same settings in the current thread. If you are
using multiple SocketTools libraries or components in your
application, you only need to enable logging once.