More notes.

[rsync.git] / rsync3.txt

diff --git a/rsync3.txt b/rsync3.txt
index 21ebaf6d7217fa89e27e61ee197c1a252262c244..42d77dcaf48c5ed53ba96e0b6d4fa504ffc0922c 100644 (file)
--- 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: