summaryrefslogtreecommitdiff
path: root/rsync3.txt
diff options
context:
space:
mode:
authorMartin Pool <mbp@samba.org>2001-09-12 14:35:39 +0000
committerMartin Pool <mbp@samba.org>2001-09-12 14:35:39 +0000
commita24e12e6dd814f7da77d121fcedf862f05f061f5 (patch)
treeabd37e4db2d80712174590e4d672264665a93c69 /rsync3.txt
parent3c6cd53b238daeeb5ba2afa87616df7cc90a429b (diff)
downloadrsync-a24e12e6dd814f7da77d121fcedf862f05f061f5.tar.gz
More notes.mbp_bk_export0
Diffstat (limited to 'rsync3.txt')
-rw-r--r--rsync3.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/rsync3.txt b/rsync3.txt
index 21ebaf6d..42d77dca 100644
--- a/rsync3.txt
+++ b/rsync3.txt
@@ -303,6 +303,13 @@ Pie-in-the-sky features:
ways for clients to smoothly and voluntarily become servers for
content they receive?
+ - Imagine a situation where the destination has a much faster link
+ to the cloud than the source. In this case, Mojo Nation downloads
+ interleaved blocks from several slower servers. The general
+ situation might be a way for a master rsync process to farm out
+ tasks to several subjobs. In this particular case they'd need
+ different sockets. This might be related to multicast.
+
Unlikely features: