restructured index somewhat

1 files changed, 35 insertions, 14 deletions

diff --git a/Demo/pdist/README b/Demo/pdist/README
index 37719cb..b3fac24 100644
--- a/Demo/pdist/README
+++ b/Demo/pdist/README
@@ -6,27 +6,47 @@ Filesystem, RCS and CVS client and server classes
 This directory contains various modules and classes that support
 remote file system operations.
 
-rrcs.py			Remote RCS client command line interface
-rrcs			Script to put in your bin directory
+CVS stuff
+---------
 
-rcvs.py			Remote CVS client command line interface
 rcvs			Script to put in your bin directory
-
-sumtree.py		Old demo for FSProxy
-cmptree.py		First FSProxy client (used to sync from the Mac)
+rcvs.py			Remote CVS client command line interface
 
 cvslib.py		CVS admin files classes (used by rrcs)
+cvslock.py		CVS locking algorithms
+
+RCS stuff
+---------
+
+rrcs			Script to put in your bin directory
+rrcs.py			Remote RCS client command line interface
+
 rcsclient.py		Return an RCSProxyClient instance
 			(has reasonable default server/port/directory)
 
+RCSProxy.py		RCS proxy and server classes (on top of rcslib.py)
+
+rcslib.py		Local-only RCS base class (affects stdout &
+			local work files)
+
+FSProxy stuff
+-------------
+
+sumtree.py		Old demo for FSProxy
+cmptree.py		First FSProxy client (used to sync from the Mac)
 FSProxy.py		Filesystem interface classes
-RCSProxy.py		RCS interface classes
+
+Generic client/server stuff
+---------------------------
 
 client.py		Client class
 server.py		Server class
 
 security.py		Security mix-in class (not very secure I think)
 
+Other generic stuff
+-------------------
+
 cmdfw.py		CommandFrameWork class
 			(used by rcvs, should be used by rrcs as well)
 
@@ -89,12 +109,13 @@ Server in order to match the class names.
 
 
 *** Security warning: this version requires that you have a file
-$HOME/.python_keyfile at the server and client side containing two comma-
-separated numbers.  The security system at the moment makes no guarantees
-of actuallng being secure -- however it requires that the key file
-exists and contains the same numbers at both ends for this to work.
-(You can specify an alternative keyfile in $PYTHON_KEYFILE).
+$HOME/.python_keyfile at the server and client side containing two
+comma- separated numbers.  The security system at the moment makes no
+guarantees of actuallng being secure -- however it requires that the
+key file exists and contains the same numbers at both ends for this to
+work.  (You can specify an alternative keyfile in $PYTHON_KEYFILE).
 Have a look at the Security class in security.py for details;
 basically, if the key file contains (x, y), then the security server
-class chooses a random number z (the challenge) in the range 10..100000
-and the client must be able to produce pow(z, x, y) (i.e. z**x mod y).
+class chooses a random number z (the challenge) in the range
+10..100000 and the client must be able to produce pow(z, x, y)
+(i.e. z**x mod y).