duplicity-team team mailing list archive

[edso <edgar.soldin@xxxxxx>]

On 23.08.2011 20:02, Michael Terry wrote:
> That is a good and sensible idea, but the current backend.list architecture isn't well suited for that, performance wise.
> 
> (A) We can't ask for information about just one file, we have to list all files each time

how about memorizing the size and compare that with the list in the end

> (B) We can't ask for size information.  We'd have to download the file again.

at least ftp/sftp offer that information. would it be difficult to implement that as eg. list_extended?

> 
> Both could be solved by after each upload, just downloading the file again and comparing to the original to 'prove' the round trip worked.  That's a decent idea, actually, just seems a lot less performant.

what makes it not decent at all. For the same time & bandwidth i can (already do) do a verify afterwards. it'd make only sense if we could plausibility check the remote site
 i guess... ede/duply.net

>  
> I could whip that up, depending on interest.  Ken?

-- 
https://code.launchpad.net/~mterry/duplicity/early-catch-498933/+merge/72607
Your team duplicity-team is requested to review the proposed merge of lp:~mterry/duplicity/early-catch-498933 into lp:duplicity.