Okay, in the light of day and being a little fresher, I see what is going on.
Under SFTP, the resumption DOES work correctly, and the large test file, intentionally broken, is completed. What fails is that, unlike FTP, if the file is already complete on the server, it gets corrupted in the manner described (i.e, becomes an empty file.) With a batch (i.e, folder) upload, I don’t expect the end user to know exactly where the break occurred. With FTP we can restart the batch, and it simply passes over each completed file till it finds the point left off. Gives me some ideas, and also gives me some incentive to put in a window to read debug data (this particular project is actually pretty new.) Should have done that in the first place :-) On Nov 17, 2017, at 1:54 AM, Christian Schmitz <supp...@monkeybreadsoftware.de> wrote: > > As far as I see in library code, seeking for resume is implemented. > Of course server needs to respond to file size query. If that fails, it > starts a new upload. ----- "Drama is life with the dull bits cut out." -Alfred Hitchcock Jerry Fritschle jerryfritsc...@icloud.com _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list mbsplugins@monkeybreadsoftware.info https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
