summaryrefslogtreecommitdiff
path: root/TODOS
diff options
context:
space:
mode:
authorAndreas Baumann <abaumann@yahoo.com>2011-11-05 11:35:32 +0100
committerAndreas Baumann <abaumann@yahoo.com>2011-11-05 11:35:32 +0100
commite9ff920e10a7f529625a7ba2471b61cc07d21229 (patch)
tree13a669eb5b286e220114fbf55db9a21a078fcb38 /TODOS
parent2e5f2a0fb1d0bdb78d43a86d2f51904a23a6670c (diff)
downloadwolfbones-e9ff920e10a7f529625a7ba2471b61cc07d21229.tar.gz
wolfbones-e9ff920e10a7f529625a7ba2471b61cc07d21229.tar.bz2
more doc cleanup
Diffstat (limited to 'TODOS')
-rw-r--r--TODOS39
1 files changed, 37 insertions, 2 deletions
diff --git a/TODOS b/TODOS
index 1b3fdad..964925a 100644
--- a/TODOS
+++ b/TODOS
@@ -26,5 +26,40 @@
- popt is localized
- argtable is not, but is very simple
- also gengetopt has a stub getopt/getopt_long which can be i18n-ized
-- merging of mc files (we want to export only the MC file so it can
- be merged)
+ - merging of mc files (we want to export only the MC file so it can
+ be merged)
+- daemon
+ - check against things done in other libraries
+ - POCO ServiceApplication
+ - libdaemon
+ - do a security survey
+ - block signals around atomar pipe reads and writes
+ - have a good look at the openradius server, there
+ seem to be important points there to handle in a
+ daemon
+ - OpenBSD 4.2 croaks about C++ style gengetopt prototypes
+- logger
+ - 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 console logger:
+ - why is it always English? what settings influence the language choosen?
+ - Windows event logger
+ - audit event log types, especially the effects on syslog and the upper
+ abstraction layer
+ - 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 (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? 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!