[Zodb-checkins] CVS: ZEO/doc - ZopeREADME.txt:1.1.2.2

[Jeremy Hylton]

Update of /cvs-repository/ZEO/doc
In directory cvs.zope.org:/tmp/cvs-serv28272

Modified Files:
      Tag: ZEO2-branch
	ZopeREADME.txt 
Log Message:
minor changes & an XXX comment



=== ZEO/doc/ZopeREADME.txt 1.1.2.1 => 1.1.2.2 ===
 
     The start script provides a number of options not documented here.
-    See docs/start.txt for more information.
+    See doc/start.txt for more information.
         
   Running Zope as a ZEO client
 
@@ -40,9 +40,7 @@
     ClientStorage::
 
       from ZEO.ClientStorage import ClientStorage
-      Storage = ClientStorage(('',port_number))
-
-    (See the misc/custom_zodb.py for an example.)
+      Storage = ClientStorage(('', port_number))
 
     You can specify a host name (rather than '') if you want.  The port
     number is, of course, the port number used to start the storage
@@ -50,8 +48,8 @@
 
     You can also give the name of a Unix domain socket file::
 
-      import ZEO.ClientStorage
-      Storage=ZEO.ClientStorage.ClientStorage(filename)
+      from ZEO.ClientStorage import ClientStorage
+      Storage = ClientStorage(filename)
 
     There are a number of configuration options available for the
     ClientStorage. See doc/ClientStorage.txt for details.
@@ -62,22 +60,23 @@
     needed so that unique cache name files can be computed.  Otherwise,
     the client cache is stored in temporary files which are removed when
     the ClientStorage shuts down.  For example, to start two Zope
-    processes with unique caches, use something like:
+    processes with unique caches, use something like::
 
       python z2.py -P8700 ZEO_CLIENT=8700
       python z2.py -P8800 ZEO_CLIENT=8800
 
   Zope product installation
 
+    XXX Does this still apply?
+
     Normally, Zope updates the Zope database during startup to reflect
     product changes or new products found. It makes no sense for
     multiple ZEO clients to do the same installation. Further, if
     different clients have different software installed, the correct
     state of the database is ambiguous.
 
-    Starting in Zope 2.2, Zope will not modify the Zope database
-    during product installation if the environment variable ZEO_CLIENT
-    is set. 
+    Zope will not modify the Zope database during product installation
+    if the environment variable ZEO_CLIENT is set.
 
     Normally, Zope ZEO clients should be run with ZEO_CLIENT set so
     that product initialization is not performed.