pcs 98/02/09 03:10:32
Modified: . STATUS
Log:
What a surprise.... more votes!
Revision Changes Path
1.20 +11 -11 apache-2.0/STATUS
Index: STATUS
===================================================================
RCS file: /export/home/cvs/apache-2.0/STATUS,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- STATUS 1998/02/08 12:05:54 1.19
+++ STATUS 1998/02/09 11:10:31 1.20
@@ -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, Ben +1
+ Status: Jim +1, Ken +1, Marc +1, MarkC +1, Ben +1, Paul +1
* The "autoconf toolset" should include all three: autoconf, automake, and
libtool.
@@ -51,7 +51,7 @@
* revamped process model (Dean's proposal)
Dean says: it's hard to do the multithreading work cleanly without
considering a bunch of this
- Status: Marc +1 on much of it; threads aren't enough for perf. MarkC +1
+ Status: Marc +1 on much of it; threads aren't enough for perf. MarkC
+1, Paul +1
* new layered I/O.
Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1,
Ralf +1, MarkC +1, Ben +1
@@ -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, Ben +1
+ Status: Dean +1, Marc +1, Ben +1, Paul +1
* API work
@@ -81,7 +81,7 @@
Status: Ken +1
. documented API
- Status: Ken +1, Sameer +1, Marc +1, Ralf +1
+ Status: Ken +1, Sameer +1, Marc +1, Ralf +1, Paul +1
. just new API phases
Status: Brian +1, Jim +1, Sameer +1 (just the "gaping holes"),
@@ -89,29 +89,29 @@
. change API 'phase' model to use module-registered hooks rather
than a fixed static structure
- Status: Ken +1, Ralf +1, MarkC +1
+ Status: Ken +1, Ralf +1, MarkC +1, Paul +1
. use virtual functions for module hooks
- Status: Ben +1
+ Status: Ben +1, Paul -1
. clearly identify API functions by renaming them
- Status: Ken +1, Ralf +1, Ben +1
+ Status: Ken +1, Ralf +1, Ben +1, Paul +1 (plus back compat.)
. backward compatibility with 1.3 (just require a recompile)
if functions get renamed, old names retained as wrappers
- Status: Paul +1, Sameer +1, Marc +1, Ralf +1, MarkC +1
+ Status: Paul +1, Sameer +1, Marc +1, Ralf +1, MarkC +1, Paul +1
. make API call syntax rational (e.g., all r*() routines list r
as their first argument, et cetera)
- Status: Ken +1, Ralf +0
+ Status: Ken +1, Ralf +0, Paul +0
* new configuration language
- Status: Dean +1, Marc +1, Ralf +0, Ben +1
+ Status: Dean +1, Marc +1, Ralf +0, Ben +1, Paul +0
* rewrite in C++
. Yes: Ben +1
. doesn't like the idea, but is open to it: Marc +1, Ralf +1
- . No way ever: MarkC +1
+ . No way ever: MarkC +1, Paul +1
Closed issues:
