From: Manoj Kasichainula <manoj@apache.org>
Date: Tue, 2 Nov 1999 23:18:28 +0000 (+0000)
Subject: No, PalmOS doesn't have threads or any process support other
X-Git-Tag: 1.3.10~192
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e82c1502efaf1fc2eecb82fcd39feaed5e0696d7;p=thirdparty%2Fapache%2Fhttpd.git

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.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84094 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/STATUS b/STATUS
index 80a27ce867c..4ab0974e031 100644
--- a/STATUS
+++ b/STATUS
@@ -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 @@ Plan:
 
 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 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 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 @@ Other bugs that need fixing:
 
     * 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.