[minion-cvs] Allude to fragment reassembly in README; bump version t...

[nickm@seul.org (Nick Mathewson)]

Update of /home/minion/cvsroot/src/minion
In directory moria.mit.edu:/tmp/cvs-serv13536

Modified Files:
	README setup.py 
Log Message:
Allude to fragment reassembly in README; bump version to 0.0.7rc1

Index: README
===================================================================
RCS file: /home/minion/cvsroot/src/minion/README,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -d -r1.74 -r1.75
--- README	7 Mar 2004 06:33:56 -0000	1.74
+++ README	8 Mar 2004 03:27:31 -0000	1.75
@@ -467,6 +467,14 @@
       export http_proxy=http://proxy:3128/
       mixminion send -D yes
 
+If you have a very large message to send, and the recipient also has
+mixminion software, you can use the "--deliver-fragments" option to prevent
+the last server in the chain from trying to reassemble the message.  (This is
+automatic when sending a reply.)  Later, when the recipient runs "mixminion
+decode" to retrieve the fragment contents, the fragments will be stored in an
+internal pool until enough have been retrieved to reassemble the message.
+Clients can manipulate this fragment pool with "mixminion list-fragments",
+"mixminion purge-fragments", and "mixminion reassemble".
 
 VI. HOW TO RUN YOUR OWN MIXMINION SERVER
 ========================================

Index: setup.py
===================================================================
RCS file: /home/minion/cvsroot/src/minion/setup.py,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -d -r1.93 -r1.94
--- setup.py	7 Mar 2004 21:07:42 -0000	1.93
+++ setup.py	8 Mar 2004 03:27:31 -0000	1.94
@@ -6,9 +6,9 @@
 #
 #   Current Mixminion version
 #
-VERSION = '0.0.7alpha2'
+VERSION = '0.0.7rc1'
 # System: 0==alpha, 50==beta, 98=pre, 99==release candidate, 100==release
-VERSION_INFO = (0,0,7,0,2)
+VERSION_INFO = (0,0,7,99,1)
 
 # Check the version.  We need to make sure version_info exists before we
 # compare to it: it was only added as of Python version 1.6.