Simplified the newly added test so that it should stop sporadically

[rsync.git] / csprotocol.txt

diff --git a/csprotocol.txt b/csprotocol.txt
index bd81de1d53f4aef9e86d6e2d2528da8082e401f0..fc388202396a2bb015220226895858212461de7c 100644 (file)
--- a/csprotocol.txt
+++ b/csprotocol.txt
@@ -61,7 +61,22 @@ multiplexing layer across the socket.  The main point of this is to
 allow the server to asynchronously pass errors back, while still
 allowing streamed and pipelined data.
 
 allow the server to asynchronously pass errors back, while still
 allowing streamed and pipelined data.
 

+Unfortunately, the multiplex protocol is not used at every stage.  We
+start up in plain socket mode and then change over by calling
+io_start_buffering.  Of course both the client and the server have to
+do this at the same point.
+

 The server then talks to the client as normal across the socket,
 passing checksums, file lists and so on.  For documentation of that,
 stay tuned (or write it yourself!).
 
 The server then talks to the client as normal across the socket,
 passing checksums, file lists and so on.  For documentation of that,
 stay tuned (or write it yourself!).
 

+
+
+------------
+Protocol version changes
+
+25      (2001-08-20, 2.4.7pre2) 
+
+        Send an explicit "@RSYNC EXIT" command at the end of the
+        module listing.  We never intentionally end the transmission
+        by just closing the socket anymore.