diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-10-14 14:34:05 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-10-14 14:34:05 -0400 |
| commit | ec23c75632cf1b8e4e3d5049a2c0a7623a9ae958 (patch) | |
| tree | 4dc0f7a7461227a48641ef0d04d2d8b27315cdbd /doc/design/assistant | |
| parent | 8fa7f0f198e70231f64cf908bdd55e270f45145f (diff) | |
avoid queuing transfers for remotes after syncing to them is paused
This avoids the expensive transfer scan relying on its list of remotes
to scan being accurate throughout, which it will not be when the user
pauses syncing to a remote.
I feel it's ok to queue transfers to *any* known remote, not just the ones
being scanned.
Note that there are still small races where after syncing to a remote is
paused, a transfer can be queued for it. Not just in the expensive transfer
scan, but in the cheap failed transfer scan, and elsewhere.
Diffstat (limited to 'doc/design/assistant')
| -rw-r--r-- | doc/design/assistant/webapp.mdwn | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/design/assistant/webapp.mdwn b/doc/design/assistant/webapp.mdwn index f3d959a33..106e7b1f6 100644 --- a/doc/design/assistant/webapp.mdwn +++ b/doc/design/assistant/webapp.mdwn @@ -8,8 +8,6 @@ The webapp is a web server that displays a shiny interface. This is quite likely because of how the div containing transfers is refereshed. If instead javascript was used to update the progress bar etc for transfers with json data, the buttons would work better. -* Disabling syncing to a remote doesn't stop any running transfer scan, - which can still queue uploads or downloads to the remote. * Transfers from a remote with syncing disabled show as from "unknown". (Note that it's probably not practical to prevent a remote with syncing disabled from initiating transfers, so this can happen.) |