Removed references to ZopeHTTPServer.

doc/FAQ.txt

@@ -48,8 +48,7 @@ Zope Installation Frequently Asked Questions
        on files and directories in your Zope installation. The var
        subdirectory of your installation and everything therein MUST be 
        writable by the user which runs cgi scripts on your web server 
-       (usually nobody if you are using PCGI, usually your userid if you
-       are using ZopeHTTPServer)
+       (usually nobody if you are using PCGI.)
        
        If you have ensured that the PCGI info file is correct and that all
        permissions are correct, you can look in the /var/tmp directory of

doc/INSTALL.txt

@@ -22,9 +22,6 @@ Running Zope
     threads. ZServer is currently in beta, so this may not be a good
     choice for production systems.
 
-  - You can use the built-in ZopeHTTP web server.  This option is
-    no longer recommended.
-
   - You can use the PCGI publisher with an existing web server. 
     This is currently the recommended way to run Zope for production
     systems. 
@@ -33,8 +30,7 @@ Choosing your database
 
   We currently support two Zope databases, ZODB 2 and ZODB 3.  To use
   ZODB 3 use ZServer via the z2.py script described below.  To use
-  ZODB 2, use the simple ZopeHTTP server or use PCGI publisher 
-  (without ZServer).
+  ZODB 2, use the PCGI publisher (without ZServer).
 
   (Alternatives for the curious and ZPublisher aware:
 
@@ -42,9 +38,8 @@ Choosing your database
       described below by providing the -2 command-line option to
       z2.py. 
 
-    - You can use ZODB 3 with the ZopeHTTPServer and the
-      PCGI publisher by changing the published module to
-      Zope. 
+    - You can use ZODB 3 with the PCGI publisher by changing the
+      published module to Zope.
   )
 
 Quick Start
@@ -172,13 +167,10 @@ Setting permissions on the var directory.
   running Zope you should ensure that you give adequate permissions
   to the Zope var directory for the userid Zope will run under.
 
-  Depending on how you choose to run Zope you will need to give different
-  permissions to the var directory. For example if you are using
-  ZopeHTTPServer which normally runs as your userid, you need only ensure
-  that your userid has read and write permissions to the var directory.
-  If you use Zope with an existing web server, it will probably run Zope
-  as 'nobody'. In this case 'nobody' needs read and write permissions to
-  the var directory.
+  Depending on how you choose to run Zope you will need to give
+  different permissions to the var directory.  If you use Zope with an
+  existing web server, it will probably run Zope as 'nobody'. In this
+  case 'nobody' needs read and write permissions to the var directory.
 
   If you change the way you run Zope you may need to modify the permissions
   of the var directory and the files in it to allow Zope to read and write
@@ -198,27 +190,6 @@ Using ZServer
   approach is preferred to avoid having to reconfigure the z2.py script
   after a software update. 
 
-  Notes
-
-    * 'start.py' is now depricated, use 'z2.py' instead.
-
-    * 'zinit.py' is now depricated, use 'z2.py' with 'zdeamon.py' instead.
-
-Using Zope with ZopeHTTPServer
-
-  ZopeHTTPServer is a simple web server written in Python and it
-  allows you to run Zope without using PCGI and another web server.
-  The build script automatically creates a shell script named 'start'
-  which will run the built-in server. To start Zope using ZopeHTTPServer 
-  cd to the Zope directory and issue the command::
-
-    ./start
-
-  Now you should be able to access Zope through the web, just like with
-  ZServer::
-
-    http://localhost:9673/manage
-
 Starting Zope with an existing web server
 
   See the WEBSERVERS.txt file for more information about configuring Zope