|
Check-in Number:
|
1170 | |
| Date: |
2001-Oct-12 14:17:50 (local)
2001-Oct-12 12:17:50 (UTC) |
| User: | rse |
| Branch: | |
| Comment: |
remember Thomas' issues |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/l2/TODO 1.28 -> 1.29
--- TODO 2001/10/05 10:40:17 1.28
+++ TODO 2001/10/12 12:17:50 1.29
@@ -2,6 +2,32 @@
OSSP L2
=======
+- thl: log facility
+ To debug an application, sometimes it's overkill to log everything at
+ DEBUG level. I see an improvement when an additional facility can be
+ specified. Example: DEBUG/LMTP but don't care about NNTP in the
+ lmtp2nntp program. Possibly could be implemented as a second mask.
+ -> needs more consideration before implementation should start (rse)
+
+- thl: buffer fork() awareness
+ When the process forks, the buffer is duplicated. Currently this means
+ the buffer has to be flushed in advance or the content is dumped twice.
+ If the buffer would remember the pid of the last writer, it could
+ discard the contents of the buffer when the pid changes. This is because
+ the parent retains the pid and the buffer content while the child
+ changes the pid and discards the content. Should be an optionial feature.
+ -> can be immediately implemented (rse)
+
+- thl: prelog
+ I want to log everything even things that happen before L2 is
+ initialized. Complicated, i know. Maybe the log function should buffer
+ everything as long as a NULL l2-context is passed and if ever a non-NULL
+ context is passed every remembered message should be logged afterwards
+ or if destroy/ flush is executed with a NULL-context it should print the
+ buffered stuff to stderr.
+ -> can be immediately implemented, but one has to be carefully here.
+ Seems like I want to think about this a little bit more in-depth. (rse)
+
RSE:
- channel API cleanup: open semantics
- bind and udp parameters in socket channel
|
|
