diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-08-29 13:41:47 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-08-29 13:41:47 -0400 |
| commit | 07de26ed7bc9ad772104008a9bb63fe455e0255d (patch) | |
| tree | 0338e8a993fe1cdfd0f93956e94b85eecfec71be /doc/design/assistant/syncing.mdwn | |
| parent | f533f2e79bb01dc2dd8b4e2da7c8eae916bd2e5f (diff) | |
simple transfer queue display cleanup
Don't display redundant queued downloads. The only problem with this is
that it reduces the total number of queued transfers the webapp displays.
Diffstat (limited to 'doc/design/assistant/syncing.mdwn')
| -rw-r--r-- | doc/design/assistant/syncing.mdwn | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/doc/design/assistant/syncing.mdwn b/doc/design/assistant/syncing.mdwn index f1be3d223..ad34a91bc 100644 --- a/doc/design/assistant/syncing.mdwn +++ b/doc/design/assistant/syncing.mdwn @@ -3,15 +3,6 @@ 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. 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? * 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 |