summaryrefslogtreecommitdiff
path: root/doc/chunking.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-07-27 18:52:42 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-07-27 18:56:32 -0400
commitf6e7037c0ccdf646d1ca955c48cece814f5700a4 (patch)
tree035070a47d5bac76e36271507a09aea23ef3ee12 /doc/chunking.mdwn
parent300935948503d671ad91b943787d71dc1f6e421e (diff)
resume interrupted chunked downloads
Leverage the new chunked remotes to automatically resume downloads. Sort of like rsync, although of course not as efficient since this needs to start at a chunk boundry. But, unlike rsync, this method will work for S3, WebDAV, external special remotes, etc, etc. Only directory special remotes so far, but many more soon! This implementation will also properly handle starting a download from one remote, interrupting, and resuming from another one, and so on. (Resuming interrupted chunked uploads is similarly doable, although slightly more expensive.) This commit was sponsored by Thomas Djärv.
Diffstat (limited to 'doc/chunking.mdwn')
-rw-r--r--doc/chunking.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/chunking.mdwn b/doc/chunking.mdwn
index 1be1fbef6..d1dce317c 100644
--- a/doc/chunking.mdwn
+++ b/doc/chunking.mdwn
@@ -4,6 +4,8 @@ chunks that are stored on the remote.
This can be useful to work around limitations on the size of files
on the remote.
+Chunking also allows for resuming interrupted downloads and uploads.
+
Note that git-annex has to buffer chunks in memory before they are sent to
a remote. So, using a large chunk size will make it use more memory.