mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: key content size

Browse source
This commit is contained in:
driusan@4d47e7deeb2f5d3846792d049ed06f96a0c3ca98 2019-03-31 16:31:09 +00:00 • committed by admin
parent d70f248459
commit f250bb092d
1 changed files with 9 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/design/p2p_protocol/comment_3_72d9bd6eff2618b23e63a9422bf8c79b._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="driusan@4d47e7deeb2f5d3846792d049ed06f96a0c3ca98"
nickname="driusan"
avatar="http://cdn.libravatar.org/avatar/409b69c3ae7b431fc16129ccdadae9cd"
subject="key content size"
date="2019-03-31T16:31:09Z"
content="""
Is there a mechanism for a client to determine the size of the content pointed to by the key on the remote? How do you determine that all the content is received? If you rely on verifying sha256 (or whatever hash) of the key, I don't see any way you can tell if the object in a local annex is corrupted or just not fully received and should be updated with GET from a higher offset.
"""]]