cvs commit: apache-devsite project-plan.html

[Rodent of Unusual Size <co...@hyperreal.com>]

coar        97/06/28 01:31:19

  Modified:    .         project-plan.html
  Log:
  	Now that this is in CVS, update project-plan.html from Brian's
  	project-plan-new.html, which will next be deleted.
  
  Revision  Changes    Path
  1.2       +32 -37    apache-devsite/project-plan.html
  
  Index: project-plan.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/project-plan.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -C3 -r1.1 -r1.2
  *** project-plan.html	1997/06/17 10:43:32	1.1
  --- project-plan.html	1997/06/28 08:31:18	1.2
  ***************
  *** 17,68 ****
    
    <P>
    
  ! <H2>1.2</H2>
    
    <UL>
  ! <LI>Full HTTP/1.1 support in all areas except the proxy module.
  ! <LI>More tolerant config-file parsing
  ! <LI>Serious dynamic loading support, so that binary distributions can have all
  !  modules compiled and can be used even by folks without compilers of their own.
  ! <LI>Standardized PUT support, at least a perl script included with the distribution.
  ! <LI>regular expression library in the core, rather than in numerous
  ! different modules.
  ! <LI>give an "Option", like "IncludesNoExec", except allow for CGI includes,
  ! not CMD includes.
  ! <LI>Logging enhancements
  !   <UL>
  !   <LI>Separate logs for stderr and server error messages
  !   <LI>Enable all virtual hosts to error-log to the same log, in ways 
  ! 	which distinguish entries.
  !   <LI>Syslog, with different debugging levels, a la named or sendmail
  !   <LI>Log rotation without restarting children.
  ! 
  !   <LI>Add total transfer time (amount of time it took to deliver file, from end of request header submission) variable to mod_log_config
  !   <LI>Dropping of "mod_log_common" in favor of "mod_log_config", making sure it's backwards-compatible.
  !   <LI>Add "%v" variable for virtualhosts to mod_log_config 
  !   <LI>Maybe look for a way to allow modules to expose variables for logging?  I.e. "%(mod_cookie:cookie)m"
  !   </UL>
  ! <LI>Support for CERN-style imagemaps?  http://www.w3.org/pub/WWW/Daemon/User/CGI/HTImageDoc.html#config.
  ! <LI>Ben's "graceful restart" code
  ! <LI>RST's "lingering close" code
  ! <LI>Enforcement of an "Apache Style" for code.
  ! <LI>mod_status cleanups and enhancements.
  ! <LI>Using "mod_uri_rewrite" in place of a couple other modules.
    </UL>
    
    
    <H2>2.0</H2>
    
    <UL>
    <LI>Multithreading
  ! <LI>GNU autoconf-based portability
  ! <LI>Through the use of autoconf, port to Windows NT
  ! <LI>Fully 1.1 compliant proxy module.
  ! <LI>Protocol abstraction layer, so that different protocol implementations can be distributed as a module.
  ! <LI>Scripted installation process, i.e. one that asks questions about
  ! the site and generates the conf files appropriately
  ! <LI>More than one transferlog per virthost, each with its own transferformat.
  ! <LI>Check returns from all system calls: read, write, etc. 
    <LI>More API hooks:
    <UL>
    	<LI>Post config-read; so we can check consistency between
  --- 17,47 ----
    
    <P>
    
  ! <H2>Proposed schedule:</H2>
    
    <UL>
  !   <LI>15 Jul: 1.3 b1
  !   <LI>30 Jul: finalize design of 2.0
  !   <LI>15 Aug: 1.3 final
  !   <LI>30 Aug: 2.0b1
  !   <LI>30 Oct: 2.0 final.
    </UL>
    
  + <H2>1.3</H2>
  + 
  + <UL>
  + <LI>Port to NT, multithreading on NT only.
  + <LI>Various performance enhancements.
  + <LI>Various bugfixes/tweaks as mentioned in [STATUS] files.
  + <LI>When 1.3 is ready for beta, the above small tweaks stop.
  + </UL>
    
    <H2>2.0</H2>
    
    <UL>
    <LI>Multithreading
  ! <LI>Enforcement of an "Apache Style" for code.
  ! <LI>Configuration API, so that different configuration loaders can be written (Perl, Java, etc.)
    <LI>More API hooks:
    <UL>
    	<LI>Post config-read; so we can check consistency between
  ***************
  *** 74,83 ****
  --- 53,72 ----
              and quality values.
            <LI>Up to 4 placeholders for future use ?
    </UL>
  + <LI>Logging enhancements
  +   <UL>
  +   <LI>Separate logs for stderr and server error messages
  +   <LI>Enable all virtual hosts to error-log to the same log, in ways 
  + 	which distinguish entries.
  +   <LI>Syslog, with different debugging levels, a la named or sendmail
  +   </UL>
  + <LI>Fully 1.1 compliant proxy module.
  + <LI>Protocol abstraction layer, so that different protocol implementations can be distributed as a module.
    </UL>
    
    <H2>2.1</H2>
    <UL>
  + <LI>Check returns from all system calls: read, write, etc. 
    <LI>Nicer Access Control (allow "OneOf","AND","OR" ala NCSA)
    <LI>Named Access Methods
    <LI>Implementation of the "LINK" Method 
  ***************
  *** 87,92 ****
  --- 76,87 ----
    <LI>Data store abstraction API?  So we're not always presuming we sit on top of a filesystem.
    <LI>Enable logging of all "POST"ed data - for commercial-database-like
    backups and replay ability. 
  + <LI>Support for CERN-style imagemaps?  http://www.w3.org/pub/WWW/Daemon/User/CGI/HTImageDoc.html#config.
  + <LI>give an "Option", like "IncludesNoExec", except allow for CGI includes,
  + not CMD includes.
  + <LI>Serious dynamic loading support, so that binary distributions can have all
  +  modules compiled and can be used even by folks without compilers of their own.
  + <LI>Standardized PUT support, at least a perl script included with the distribution.
    </UL>
    
    <H2>3.0</H2>