summaryrefslogtreecommitdiff
path: root/doc/design/assistant/syncing.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-11-30 13:48:44 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-11-30 13:48:44 -0400
commit68bda41035ee832d85b2e4aab22986ea049493a2 (patch)
tree81de50f9d80a9cba26b52d89c6abbccd60ac3a3a /doc/design/assistant/syncing.mdwn
parentb19aa7c52986b1af8f8a32515d35884aa7aa39f5 (diff)
read through all design docs and updated done items
Diffstat (limited to 'doc/design/assistant/syncing.mdwn')
-rw-r--r--doc/design/assistant/syncing.mdwn9
1 files changed, 1 insertions, 8 deletions
diff --git a/doc/design/assistant/syncing.mdwn b/doc/design/assistant/syncing.mdwn
index a7592d84b..3274c634a 100644
--- a/doc/design/assistant/syncing.mdwn
+++ b/doc/design/assistant/syncing.mdwn
@@ -18,13 +18,9 @@ all the other git clones, at both the git level and the key/value level.
airport somewhere.
* Find a way to probe available outgoing bandwidth, to throttle so
we don't bufferbloat the network to death.
-* Investigate the XMPP approach like dvcs-autosync does, or other ways of
- signaling a change out of band.
* Add a hook, so when there's a change to sync, a program can be run
and do its own signaling.
* --debug will show often unnecessary work being done. Optimise.
-* This assumes the network is connected. It's often not, so the
- [[cloud]] needs to be used to bridge between LANs.
* Configurablity, including only enabling git syncing but not data transfer;
only uploading new files but not downloading, and only downloading
files in some directories and not others. See for use cases:
@@ -41,14 +37,11 @@ all the other git clones, at both the git level and the key/value level.
working copy and checks each file. That probably needs to be done once,
but further calls to the TransferScanner could eg, look at the delta
between the last scan and the current one in the git-annex branch.
-* Ensure that when a remote receives content, and updates its location log,
- it syncs that update back out. Currently, it does not, unless the master
- branch also changed. Prerequisite for:
* After git sync, identify new content that we don't have that is now available
on remotes, and transfer. (Needed when we have a uni-directional connection
to a remote, so it won't be uploading content to us.) Note: Does not
need to use the TransferScanner, if we get and check a list of the changed
- files.
+ files. done?
* [[use multiple transfer slots|todo/Slow_transfer_for_a_lot_of_small_files.]]
* The TransferQueue's list of deferred downloads could theoretically
grow without bounds in memory. Limit it to a given number of entries,