From 99ead7bcf43a831bb1a884140a23ceefc90c8ef0 Mon Sep 17 00:00:00 2001 From: Chel Date: Sun, 26 Jan 2020 22:48:09 +0000 Subject: [PATCH] Added a comment --- ...4_e766f725e22ea0a38ac2277e08fd3839._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/key_checksum_from_chunk_checksums/comment_4_e766f725e22ea0a38ac2277e08fd3839._comment diff --git a/doc/todo/key_checksum_from_chunk_checksums/comment_4_e766f725e22ea0a38ac2277e08fd3839._comment b/doc/todo/key_checksum_from_chunk_checksums/comment_4_e766f725e22ea0a38ac2277e08fd3839._comment new file mode 100644 index 0000000000..82e760c8cf --- /dev/null +++ b/doc/todo/key_checksum_from_chunk_checksums/comment_4_e766f725e22ea0a38ac2277e08fd3839._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="Chel" + avatar="http://cdn.libravatar.org/avatar/a42feb5169f70b3edf7f7611f7e3640c" + subject="comment 4" + date="2020-01-26T22:48:07Z" + content=""" +Another theoretical use case (not available for now, but maybe for the future): +verify with checksums parts of the file and re-download only those parts/chunks, that are bad. +For this you need a checksum for each chunk and a \"global\" checksum in key, that somehow incorporates all these chunk checksums. +An example of this is Tiger Tree Hash in file sharing. + +When I used the SHA256 backend in my downloads, I often wondered that the long process of checksumming a movie +or an OS installation .iso is not ideal. Because if the file download is not finished, I get the wrong checksum, +and the whole process needs to be repeated. + +And in the future git-annex can integrate a FUSE filesystem and literally store just chunks of files, +but represent files as a whole in this virtual filesystem view. +"""]]