[Zodb-checkins] CVS: ZEO/docs - ClientStorage.txt:1.2.2.1

Jeremy Hylton jeremy@zope.com
Thu, 3 Oct 2002 19:10:16 -0400


Update of /cvs-repository/ZEO/docs
In directory cvs.zope.org:/tmp/cvs-serv8567/docs

Modified Files:
      Tag: ZODB3-3_1-branch
	ClientStorage.txt 
Log Message:
Add read_only_fallback and make minor edits of others.


=== ZEO/docs/ClientStorage.txt 1.2 => 1.2.2.1 ===
--- ZEO/docs/ClientStorage.txt:1.2	Tue Jun 11 09:43:07 2002
+++ ZEO/docs/ClientStorage.txt	Thu Oct  3 19:10:16 2002
@@ -23,7 +23,9 @@
       - a sequence of the previous two
 
     If a sequence of addresses is specified, the client will use the
-    first server from the list that it can connect to.
+    first server from the list that it can connect to, subject to the
+    constraints imposed by the optional read_only and
+    read_only_fallback keyword arguments.
 
     The ClientStorage constructor provides a number of additional
     options (arguments). The full list of arguments is:
@@ -36,7 +38,7 @@
       default name for both the server and client is '1'.
 
     cache_size -- The number of bytes to allow for the client cache.
-      The default is 20,000,000.  A large cache can significantly
+      The default is 20MB.  A large cache can significantly
       increase the performance of a ZEO system.  For applications that
       have a large database, the default size may be too small.
 
@@ -93,3 +95,8 @@
 
       Each storage served by a ZEO server can be configured as either
       read-write or read-only.
+
+    read_only_fallback -- A flag indicating whether a read-only
+      remote storage should be acceptable as a fallback when no
+      writable storages are available.  Defaults to false.  At most
+      one of read_only and read_only_fallback should be true.