From b654597c2f2587535205c1a260ae0b01cdfb4196 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Mar 2018 17:24:18 -0400 Subject: [PATCH] urk, this is hard --- ...isabling_verification_of_transfer_over_p2p_protocol.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/todo/support_disabling_verification_of_transfer_over_p2p_protocol.mdwn b/doc/todo/support_disabling_verification_of_transfer_over_p2p_protocol.mdwn index 9fbf69216a..9d59bef8da 100644 --- a/doc/todo/support_disabling_verification_of_transfer_over_p2p_protocol.mdwn +++ b/doc/todo/support_disabling_verification_of_transfer_over_p2p_protocol.mdwn @@ -14,3 +14,9 @@ as it was transferred, and "0" when it did. My first attempt to implement this failed miserably due to a Free monad type check problem I could not see a way around. + +Also, resumes make this difficult. What if a file starts to be transferred, +gets changed while it's transferred so some bad bytes are sent, then the +transfer is interrupted, and later is resumed from a different remote +that has the correct content. How can it tell that the bad data was sent +in this case?