added a lot more readmes and todos (around porting, windows, Sun CC compiler and logging)

2 files changed, 38 insertions, 2 deletions

diff --git a/docs/log/README b/docs/log/README
new file mode 100644
index 0000000..2c0de91
--- /dev/null
+++ b/docs/log/README
@@ -0,0 +1,35 @@
+Windows Logging:
+
+Problems to address here:
+- event logging is not only writting a string, there are event numbers,
+  message resource DLLs and FormatString involved here. This has to be
+  nicely integrated with the snprintf-way of logging on Unix/syslog.
+- EventLog can be done locally or remotly
+- strings like event sources can be localized again
+- how are log levels mapped to event types
+- how do we make use of event log's categories.
+- and of course all has to be buildable with a simple (N)Makefile
+- integration of strings like UNC host, event source, messages and their
+  character sets without adding a string abstraction layer or funny
+  switches in the code
+- tracing data should not go to neither syslog or event log
+- there should be some protection against flooding the logs as they
+  are a system-wide scarse resource!
+
+Other projects:
+
+- .NET EventLog class
+- log4j
+- POCOs EventLogChannel
+- www.codeproject.com/KB/cpp/logdriver.aspx 
+- log4cpp
+- log4cplus
+
+All of them ignore the message resource and classes of same errors with
+different parameters. Sadly enough also the MS guys themselves (see
+184416764.html). log4j has influenced log4cpp, log4pp, logdriver (UMHO
+to the worse!).
+
+The category is usually used for mapping the coarser gained levels of
+the logging API to the event logger (POCO, log4cpp). IMHO this is better
+used for something like subsystems or components.
diff --git a/docs/log/TODOS b/docs/log/TODOS
index 2acb3af..bcbeee8 100644
--- a/docs/log/TODOS
+++ b/docs/log/TODOS
@@ -1,3 +1,4 @@
+- compare other approaches, disappointing all of them so far!
 - local localized error handling (GetLastError and strerror_r strings)
 - Windows event logger
   - audit event log types, especially the effects on syslog and the upper
@@ -20,6 +21,6 @@
   - the event logger can log binary data (as dumps), this helps to
     debug things with the right event log DLL most likely, we have
     to read more about that later.
+- there is an Windows Event Log book around which is quite big, find
+  out if it's still available
 
-links & literature:
-- there is an Windows Event Log book around which is quite big