httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ma...@hyperreal.org
Subject cvs commit: apache-2.0 STATUS
Date Tue, 02 Nov 1999 23:18:31 GMT
manoj       99/11/02 15:18:30

  Modified:    .        STATUS
  Log:
  No, PalmOS doesn't have threads or any process support other
  than a task swapper, but it has a TCP stack with non-blocking
  I/O and an event subsystem that will report on socket status
  changes. A PalmOS MPM shouldn't be too much trouble at all.
  
  Revision  Changes    Path
  1.8       +11 -2     apache-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/apache-2.0/STATUS,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -d -u -r1.7 -r1.8
  --- STATUS	1999/11/01 04:30:52	1.7
  +++ STATUS	1999/11/02 23:18:28	1.8
  @@ -1,5 +1,5 @@
   Apache 2.0 STATUS:
  -Last modified at [$Date: 1999/11/01 04:30:52 $]
  +Last modified at [$Date: 1999/11/02 23:18:28 $]
   
   Release:
   
  @@ -12,7 +12,14 @@
   
   RELEASE SHOWSTOPPERS:
   
  +    * CGI programs will stop working after a little while
  +        Status: Manoj is working on this
  +
       * suEXEC doesn't work
  +        Status: Manoj has finished an implementation, but it needs
  +        polishing. Specifically, it puts a bunch of Unix stuff into
  +        portable code.  Current patch will be sent to new-httpd upon
  +        request.
   
       * Windows NT port isn't done
           Status: Bill is working on this through his MPM work, and Ryan
  @@ -41,6 +48,8 @@
   Other bugs that need fixing:
   
       * MaxRequestsPerChild measures connections, not requests.
  +        Until someone has a better way, we'll probably just rename it
  +        "MaxConnectionsPerChild".
       
       * Regex containers don't work in an intutive way
           Status: No one has come up with an efficient way to fix this
  @@ -49,7 +58,7 @@
   
       * Areas where APRFile is being used need to be cleaned-up
   
  -    * SIGSEGV on Linux seems to only kill a thread not a whole process;
  +    * SIGSEGV on Linux seems to only kill a thread, not a whole process;
         we need to work around this, probably by bouncing the signal to
         the sigwait thread. But this will hurt debugability.
   
  
  
  

Mime
View raw message