summaryrefslogtreecommitdiff
path: root/csprotocol.txt
diff options
context:
space:
mode:
authorMartin Pool <mbp@samba.org>2001-08-22 04:14:05 +0000
committerMartin Pool <mbp@samba.org>2001-08-22 04:14:05 +0000
commit6f82f7a6f67bd9f5dd88bc3977c1f633405244f0 (patch)
treea40f9e69a4b3c54be17e7c1e35a361e9bc7eee30 /csprotocol.txt
parent33d213bb37a004b9f58642f9d186d6b68747e6d5 (diff)
downloadrsync-6f82f7a6f67bd9f5dd88bc3977c1f633405244f0.tar.gz
Add a little more protocol documentation.
Diffstat (limited to 'csprotocol.txt')
-rw-r--r--csprotocol.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/csprotocol.txt b/csprotocol.txt
index bd81de1d..b41c20fb 100644
--- a/csprotocol.txt
+++ b/csprotocol.txt
@@ -61,7 +61,14 @@ 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.
+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!).
+
+