ben 98/02/08 04:05:55
Modified: . STATUS
Log:
Revision Changes Path
1.19 +11 -8 apache-2.0/STATUS
Index: STATUS
===================================================================
RCS file: /export/home/cvs/apache-2.0/STATUS,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- STATUS 1998/02/08 10:08:17 1.18
+++ STATUS 1998/02/08 12:05:54 1.19
@@ -30,7 +30,7 @@
varies from the above such that if it's shown that the "autoconf
toolset" can do what we want, with less headache than what we
have, then we go for it)
- Status: Jim +1, Ken +1, Marc +1, MarkC +1
+ Status: Jim +1, Ken +1, Marc +1, MarkC +1, Ben +1
* The "autoconf toolset" should include all three: autoconf, automake, and
libtool.
@@ -44,9 +44,9 @@
to add more, but try not to duplicate earlier items too much.
* multithreading.
- Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1,
Ralf +1, MarkC +1
+ Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1,
Ralf +1, MarkC +1, Ben +1
- Thread Abstraction
- Status: Sameer +1, Marc +1, MarkC +1
+ Status: Sameer +1, Marc +1, MarkC +1, Ben +1
* revamped process model (Dean's proposal)
Dean says: it's hard to do the multithreading work cleanly without
@@ -54,7 +54,7 @@
Status: Marc +1 on much of it; threads aren't enough for perf. MarkC +1
* new layered I/O.
- Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1,
Ralf +1, MarkC +1
+ Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1,
Ralf +1, MarkC +1, Ben +1
. sfio
Status: Dean -1 until it's shown to be thread safe (RST claims it isn't)
@@ -73,7 +73,7 @@
can get zero-copy in the user space, which is a big win for caching
modules of all sorts. You can also support the "traditional" slow
style of stdio, which adds an extra user space copy.)
- Status: Dean +1, Marc +1
+ Status: Dean +1, Marc +1, Ben +1
* API work
@@ -91,8 +91,11 @@
than a fixed static structure
Status: Ken +1, Ralf +1, MarkC +1
+ . use virtual functions for module hooks
+ Status: Ben +1
+
. clearly identify API functions by renaming them
- Status: Ken +1, Ralf +1
+ Status: Ken +1, Ralf +1, Ben +1
. backward compatibility with 1.3 (just require a recompile)
if functions get renamed, old names retained as wrappers
@@ -103,10 +106,10 @@
Status: Ken +1, Ralf +0
* new configuration language
- Status: Dean +1, Marc +1, Ralf +0
+ Status: Dean +1, Marc +1, Ralf +0, Ben +1
* rewrite in C++
- . Yes:
+ . Yes: Ben +1
. doesn't like the idea, but is open to it: Marc +1, Ralf +1
. No way ever: MarkC +1
