>> Do you mean it could be smaller than his previous size >> when resuming a transfert ? > > Yes, that's what I mean and the question :))
If a resumed transfer is smaller than the existing file, then there is a problem ! It is likely that the start of the local file is no more the same as the copy on the server and the whole transfert is corrupted. -- [EMAIL PROTECTED] The author for the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be ----- Original Message ----- From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Thursday, August 31, 2006 9:18 PM Subject: Re: [twsocket] FTP resuming transfers > Francois PIETTE wrote: >>> I reworked the streams stuff in both FTP C/S today and >>> fixed some bugs, everything was tested sucessfully with >>> 64-bit streams. There's only one question I cannot answer >>> by myself. >>> TFileStream in mode fmOpenWrite does not set its size >>> to current position when it is destroyed. Won't it make >>> sense to set stream size explizitely to the current position >>> in the FtpCli/FtpSrv when data connection is closed >>> (although I guess that it won't work in D2 since method >>> Size exists since D3)? >>> >>> What do you think? >> >> Do you mean it could be smaller than his previous size >> when resuming a transfert ? > > Yes, that's what I mean and the question :)) > >> I don't think so. >> >> -- >> Contribute to the SSL Effort. Visit >> http://www.overbyte.be/eng/ssl.html -- >> [EMAIL PROTECTED] >> http://www.overbyte.be > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
