updated logger TODO list and README

2 files changed, 18 insertions, 23 deletions

diff --git a/docs/log/README b/docs/log/README
index 3335978..1fd0cd6 100644
--- a/docs/log/README
+++ b/docs/log/README
@@ -41,10 +41,11 @@ the logging API to the event logger (POCO, log4cpp). IMHO this is better
 used for something like subsystems or components.
 
 log4cplus is the only library to handle the current user SID.
-log4cplus adds the event source to the registry.
+
+log4cplus adds the event source to the registry in the best way.
 
 .NET at least cares to install a dummy message DLL with a %1's in them.
-Also POCO takes the one event message approach.
+Also POCO and the rest take "the one event message" approach. 
 
 Good articles:
 - http://www.codeproject.com/KB/dotnet/evtvwr.aspx
diff --git a/docs/log/TODOS b/docs/log/TODOS
index 3c7e654..06a4c20 100644
--- a/docs/log/TODOS
+++ b/docs/log/TODOS
@@ -1,29 +1,23 @@
+- rewrite and clean up, make logging channels, make logging re-entrant
+  (error in one channel should be logged on all other available channels)
 - local localized error handling (GetLastError and strerror_r strings)
 - Windows event logger
-  - categories don't work yet
   - audit event log types, especially the effects on syslog and the upper
     abstraction layer
-  - event log categories, for instance for components, the idea is that
-    an admin should be able to filter by category.
-    - some categories could be the wolf_log_level_t's as a first step,
-      especially because the event logger knows only about 4 levels of
-      errors
-  - error ids and classes, but this means they also have to be there
-    for Unix and the abstraction layer above, so no more
-    WOLF_LOG( "%s bla bla %d", ... )
-    things look more like
-    WOLF_LOG( LOG_COMP_NETWORKER, LOG_NETWORKER_ERROR_455,
-      _T( "%s bla bla bla %d", ... );
+  - replace the create_wolfmsg.pl with something more robust and not Perl
+  - make it possible to merge mc files (for appliation development)
   - parameter list dilemma of typed one (classic C) %s, %d versus
-    positional one in Windows %1 %2
-  - security identifier if we start to log to the audit log, as long
-    as we have a simple application log, we should have enough rights
-  - 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.
+    positional one in Windows %1 %2 (this is a stub implementation for now)
+    => requires a special snprintf which doesn't build one result string,
+       but results the mapped sub-strings, so we can pass them to
+       ReportEvent
   - there is an Windows Event Log book around which is quite big, find
     out if it's still available
   - the Windows messages files are avaiable (where?), should the standard
-    messages be used?
-- make sure the logger is reentrant in itself, also make sure that we log
-  errors in one of the loggers channels to all other channels
+    messages be used? And for what?
+  - should we split the category and the message DLL? There also GUID
+    DLLs for resourcen, what can they be used for?
+  - Seen links with the actual event number in the event logger with the
+    possibility to send it directly to a bug system (HTML form). This
+    would be great to have!
+