diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-08-28 17:30:48 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-08-28 17:30:48 -0400 |
| commit | c39e19053588a7a5f48641338ec3a22b1d5cf266 (patch) | |
| tree | 3190cceff6123d70d683eb41a7e3dc4aaa7c4c8f /doc/design/assistant/syncing.mdwn | |
| parent | ac15074d6e4295d31482b875deae0c4410db5d0d (diff) | |
updates
Diffstat (limited to 'doc/design/assistant/syncing.mdwn')
| -rw-r--r-- | doc/design/assistant/syncing.mdwn | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/design/assistant/syncing.mdwn b/doc/design/assistant/syncing.mdwn index f40275dff..22827bece 100644 --- a/doc/design/assistant/syncing.mdwn +++ b/doc/design/assistant/syncing.mdwn @@ -3,9 +3,18 @@ all the other git clones, at both the git level and the key/value level. ## immediate action items +* The TransferScanner queues downloads for a single file from every remote + that has it. If the first is not available, a failure alert is shown. + It should not be, if there is another remote to try. Also, it'd be nicer + to only show one queued transfer. Perhaps only queue one, and check + for other locations if it fails? Or change the queue so each transfer is + really a list of equivilant transfers. * Sometimes a Download gets queued from a slow remote, and then a fast remote becomes available, and a Download is queued from it. Would be good to sort the transfer queue to run fast Downloads (and Uploads) first. + Or, solve this along with the item above? +* For some reason, the TransferScanner is queueing transfers from remotes + that are on drives that are not mounted. (In my sound repo.) * Ensure that when a remote receives content, and updates its location log, it syncs that update back out. Prerequisite for: * After git sync, identify new content that we don't have that is now available |