Index: ossp-pkg/l2/TODO
RCS File: /v/ossp/cvs/ossp-pkg/l2/TODO,v
rcsdiff -q -kk '-r1.10' '-r1.11' -u '/v/ossp/cvs/ossp-pkg/l2/TODO,v' 2>/dev/null
--- TODO	2001/08/24 15:15:22	1.10
+++ TODO	2001/08/26 12:59:55	1.11
@@ -34,6 +34,12 @@
 o hook_write's should perhaps receive a nul-termined string
   instead of buf+size, because syslog else has to re-buffer it.
 
+QUESTIONS
+---------
+
+o Should the following line copy the string or just use the reference?
+    L2_PARAM_SET(pa[0], ident,   CHARPTR,  &cfg->pszIdent);
+
 BRAINSTORMING
 -------------
 
@@ -74,6 +80,14 @@
     erase, what happens to its data when it is over
     written or flushed...
 
+o syslog
+    many options need docu, and we should mention to
+    the user that more info is found in the man page
+    for syslog(), because after all that is what is
+    doing all the work in our implementation. Also,
+    can we really properly document these features
+    if they change from one system's syslog to the next?
+
 o errors
     when a channel fails during an operation, how
     does it report this? How should a user interpret
@@ -87,6 +101,11 @@
 - debugging is special case of logging
 - tracing is special case of debugging
 
+Kanalen:
+o Syslog Kanal
+  - Trim down to what will be used, right now the
+    channel supports ALL functionality through syslog(3)
+
 License:
 - ISC/MIT/BSD