diff options
author | 2012-10-19 13:33:11 -0400 | |
---|---|---|
committer | 2012-10-19 13:33:11 -0400 | |
commit | 830c98ee340d7e2ba069e453f73a4049bd639d7f (patch) | |
tree | 851829f58fe9e5a53818a2d60cbc577caed42f39 | |
parent | f9a24c055e589fdb5a5307f240f4417d220fd8e9 (diff) |
race
-rw-r--r-- | doc/design/assistant/transfer_control.mdwn | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/design/assistant/transfer_control.mdwn b/doc/design/assistant/transfer_control.mdwn index 129a2304d..1c31b85e7 100644 --- a/doc/design/assistant/transfer_control.mdwn +++ b/doc/design/assistant/transfer_control.mdwn @@ -17,8 +17,11 @@ something smart with such remotes. time more uploads and downloads are queued. It would be better to drop as much content as possible upfront, to keep the total annex size as small as possible. How to do that without making two expensive scans? +* The TransferWatcher's finishedTransfer function relies on the location + log having been updated after a transfer. But there's a race; if the + log is not updated in time, it will fail to drop unwanted content. -### dropping no longer preferred content TODO +### dropping no longer preferred content When a file is renamed, it might stop being preferred, so could be checked and dropped. (If there's multiple links to |