summaryrefslogtreecommitdiff
path: root/csprotocol.txt
diff options
context:
space:
mode:
authorMartin Pool <mbp@samba.org>2001-02-22 13:01:27 +0000
committerMartin Pool <mbp@samba.org>2001-02-22 13:01:27 +0000
commitfcb6d28d0bcfa9ac630ee7cf38ff08a1978ee01c (patch)
treebb52a3f2da6e86216b3133ca8591fbf8c5d29be0 /csprotocol.txt
parent62402cb14bd322ffc8fa03f20cd8b8703efe5356 (diff)
downloadrsync-fcb6d28d0bcfa9ac630ee7cf38ff08a1978ee01c.tar.gz
rsync-fcb6d28d0bcfa9ac630ee7cf38ff08a1978ee01c.tar.bz2
rsync-fcb6d28d0bcfa9ac630ee7cf38ff08a1978ee01c.zip
Note about multiplexing.
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 05b28c19..bd81de1d 100644
--- a/csprotocol.txt
+++ b/csprotocol.txt
@@ -3,6 +3,8 @@ basically a summary of clientserver.c and authenticate.c.
-- Martin Pool <mbp@samba.org>
+$Id$
+
@@ -54,6 +56,11 @@ So if the client specifies a list of files to be included or excluded,
they'll defer to existing limits specified in the server
configuration.
+At this point the client and server both switch to using a
+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.
+
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!).