httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@hyperreal.org
Subject cvs commit: apache-2.0 STATUS
Date Tue, 17 Mar 1998 15:00:25 GMT
jim         98/03/17 07:00:25

  Modified:    .        STATUS
  Log:
  Ahhh... At this rate, Apache 2.0 should be
  called Apache 2000 :)
  
  Revision  Changes    Path
  1.29      +16 -7     apache-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-2.0/STATUS,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -r1.28 -r1.29
  --- STATUS	1998/03/14 17:12:51	1.28
  +++ STATUS	1998/03/17 15:00:24	1.29
  @@ -66,6 +66,16 @@
       without.
       Status: Dean +1
   
  +  * One of the main restrictions on Apache has been that we must assume
  +    a very low-level common denominator for the OSs out there. For example,
  +    Configure is always being derided as crappy, but it is restricted,
  +    by long tradition and common sense, to only use those capabilities
  +    that existed in the System 7 'sh' (eg: no function, etc...). One
  +    possible key to Apache's success is that it does not require any
  +    more than basic UNIX tools (and an ANSI C compiler) to build,
  +    compile and run. Many of the ideas floating around for 2.0 would,
  +    by default, (drastically) change this. Is this a good idea?
  +
     FEATURE SET FOR 2.0
       Here, we decide how many of the following feature ideas we will set for
       ourselves as work items for 2.0.  We can't do everything we would want
  @@ -99,10 +109,7 @@
   
         . bstdio
   	This was written by Chris Provenzano as part of his implementation
  -	of Posix threads... Jim can place a copy of the RST-hacked
  -	version on dev.apache.org if needed and possible.
  -	   -- RST never donated his hacks to the Group.  Don't put it up for
  -	      download unless you've cleared it with him. --Brian
  +	of Posix threads.
   
         . page flipping friendly, page-sized buffer oriented, zero copy I/O
   	(In this model there are functions like readbuf() which return a
  @@ -113,7 +120,8 @@
   	style of stdio, which adds an extra user space copy.)
   	Martin asks:  Is there some software flying around where such
   		a model has been tried? Or is it a totally new technique?
  -	Status: Dean +1, Marc +1, Ben +1, Paul +1, Martin +1
  +	Jim asks: examples? Portability concerns?
  +	Status: Dean +1, Marc +1, Ben +1, Paul +1, Martin +1, Jim 0
   	Volunteers: 
   
       * API work
  @@ -124,7 +132,7 @@
   
         . documented API
   	Status: Ken +1, Sameer +1, Marc +1, Ralf +1, Paul +1, Dean +1,
  -		Martin +1
  +		Martin +1, Jim +1
   	Volunteers: Ken
   
         . just new API phases
  @@ -143,7 +151,8 @@
   	Volunteers: 
   
         . clearly identify API functions by renaming them
  -	Status: Ken +1, Ralf +1, Ben +1, Paul +1 (plus back compat.), Dean +1
  +	Status: Ken +1, Ralf +1, Ben +1, Paul +1 (plus back compat.), Dean +1,
  +		Jim +1
   	Volunteers: Ken
   
         . backward compatibility with 1.3 (just require a recompile)
  
  
  

Mime
View raw message