From f250bb092d94c2956dfeda266516235f8b86b5c6 Mon Sep 17 00:00:00 2001 From: "driusan@4d47e7deeb2f5d3846792d049ed06f96a0c3ca98" Date: Sun, 31 Mar 2019 16:31:09 +0000 Subject: [PATCH] Added a comment: key content size --- .../comment_3_72d9bd6eff2618b23e63a9422bf8c79b._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/design/p2p_protocol/comment_3_72d9bd6eff2618b23e63a9422bf8c79b._comment diff --git a/doc/design/p2p_protocol/comment_3_72d9bd6eff2618b23e63a9422bf8c79b._comment b/doc/design/p2p_protocol/comment_3_72d9bd6eff2618b23e63a9422bf8c79b._comment new file mode 100644 index 0000000000..a68ba23cc6 --- /dev/null +++ b/doc/design/p2p_protocol/comment_3_72d9bd6eff2618b23e63a9422bf8c79b._comment @@ -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. +"""]]