diff options
| author |  gl34 <gl34@web> | 2013-05-30 19:22:24 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-05-30 19:22:24 +0000 |
| commit | 1ab3eed87fe7da39bd8d73b19480378ab8127260 (patch) | |
| tree | e89119a52ac600b0664f91f4297de8bf0d50da80 /doc | |
| parent | 6b7ebf7b438e34815701be282e46855b89ef268d (diff) | |
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn b/doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn new file mode 100644 index 000000000..6eca2b64e --- /dev/null +++ b/doc/forum/glacier_-_range_retrievals_and_daily_free_retrieval_allowance.mdwn @@ -0,0 +1,3 @@ +I propose to add some functionality to git-annex, to automatically "throttle" the data retrieval from amazon glacier to stay within the daily free retrieval allowance. If someone would need to get his/her files faster, there should be an option to disable this throttling (or even better, specify the retrieval rate). + +As far as I understand glacier, this could be implemented using range retrievals. In short range retrievals enable you, to only retrieve a part of an archive in glacier. This can be used to only retrieve / request so much data, that you stay within the free retrieval allowance. ( please see [Q: Why would I retrieve only a range of an archive?](http://aws.amazon.com/glacier/faqs/#Why_would_I_retrieve_only_a_range_of_an_archive) ). |