marc 98/02/06 17:17:03
Modified: . STATUS
Log:
I'm glad I'm not in California. Here El Nino gives nice weather.
Revision Changes Path
1.14 +13 -10 apache-2.0/STATUS
Index: STATUS
===================================================================
RCS file: /export/home/cvs/apache-2.0/STATUS,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- STATUS 1998/02/06 19:59:47 1.13
+++ STATUS 1998/02/07 01:17:03 1.14
@@ -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
+ Status: Jim +1, Ken +1, Marc +1
* The "autoconf toolset" should include all three: autoconf, automake, and
libtool.
@@ -44,17 +44,17 @@
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
+ Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1
- Thread Abstraction
- Status: Sameer +1
+ Status: Sameer +1, Marc +1
* revamped process model (Dean's proposal)
Dean says: it's hard to do the multithreading work cleanly without
considering a bunch of this
- Status:
+ Status: Marc +1 on much of it; threads aren't enough for perf.
* new layered I/O.
- Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1
+ Status: Brian +1, Ken +1, Dean +1, Jim +1, Paul +1, Sameer +1, Marc +1
. sfio
Status: Dean -1 until it's shown to be thread safe (RST claims it isn't)
@@ -69,7 +69,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
+ Status: Dean +1, Marc +1
* API work
@@ -77,7 +77,7 @@
Status: Ken +1
. documented API
- Status: Ken +1, Sameer +1
+ Status: Ken +1, Sameer +1, Marc +1
. just new API phases
Status: Brian +1, Jim +1, Sameer +1 (just the "gaping holes")
@@ -91,17 +91,20 @@
. backward compatibility with 1.3 (just require a recompile)
if functions get renamed, old names retained as wrappers
- Status: Paul +1, Sameer +1
+ Status: Paul +1, Sameer +1, Marc +1
. make API call syntax rational (e.g., all r*() routines list r
as their first argument, et cetera)
Status: Ken +1
* new configuration language
- Status: Dean +1
+ Status: Dean +1, Marc +1
* rewrite in C++
- Status:
+ . Yes:
+ . doesn't like the idea, but is open to it: Marc +1
+ . No way ever:
+
Closed issues:
