|
Check-in Number:
|
1203 | |
| Date: |
2001-Oct-23 14:33:28 (local)
2001-Oct-23 12:33:28 (UTC) |
| User: | ms |
| Branch: | |
| Comment: |
New ideas and dreams about asynch, pipe, shared memory, and multithreading. |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/l2/TODO 1.33 -> 1.34
--- TODO 2001/10/23 10:05:53 1.33
+++ TODO 2001/10/23 12:33:28 1.34
@@ -69,16 +69,25 @@
via fcntl(3).
- syslog channel should support direct remote logging
- implement "filter" channel
+- idea of an asynch channel, that spawns a new process and
+ communicates with the stemming channels via shared memory
MS:
-- implement pipe channel
+- pipe channel may need a big overhaul if we redesign
+ it around the asynch channel principle
- review pipe handler for dangling descriptors
- configure only checks existance of command in non-shell mode
- find alternative to exec arguments which is hard coded to 256
- signal handler chaining, save old signal handler and call it after our own
- consider adding options such as PCRE_CASELESS to filter channel
-- implement "action" channel
+- implement "action" channel, can be based on pipe channel
- correct problem with multiple buffer channels using the timer
+- solve problem with buffer (timer), irc (ping), and buffer (autoflush), by
+ creating sleep/ping threads. The disadvantage is that we must depend on a
+ pth installation, and force the parent app to be multithreaded.
+ Alternatively, we can spawn a management process in l2_stream_create(), who
+ owns management resources globally available to all channels. Or write the
+ l2 mini-protocol :-(
ISSUES
------
|
|
