|
Check-in Number:
|
1184 | |
| Date: |
2001-Oct-14 08:21:51 (local)
2001-Oct-14 06:21:51 (UTC) |
| User: | ms |
| Branch: | |
| Comment: |
Idea of action channel to conditionally run user code depending on L2 message
stream content. |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/l2/TODO 1.29 -> 1.30
--- TODO 2001/10/12 12:17:50 1.29
+++ TODO 2001/10/14 06:21:51 1.30
@@ -56,6 +56,7 @@
- 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
ISSUES
------
@@ -147,6 +148,16 @@
o l2_ch_buffer
- write() must implicitly flush() when incoming
data is larger than remaining buffer capacity
+o l2_ch_action
+ - new action channnel could accept a regexp or L2_LEVEL as configuration,
+ and then run a callback function or exec a binary depending on incoming
+ l2 stream messages. For example, lmtp2nntp could conditionally run code
+ via the new action channel to monitor spam or alert an admin about a
+ flawed OR CURIOUs LMTP header. However, the action channel is also
+ appealling to other applications that don't run as daemons or at the
+ system level.
+ - l2_channel_config(l2Act, "regexp,run", "(nobody|cz)", "callback");
+ - l2_channel_config(l2Act, "funcptr", pfnAddtcpwrap);
License:
- ISC/MIT/BSD
|
|
