Dan wrote: >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:twsocket- >> [EMAIL PROTECTED] On Behalf Of Arno Garrels >> Sent: 31 March 2007 12:24 >> To: ICS support mailing >> Subject: Re: [twsocket] Questions about FTPClient >> >> Dan wrote: >>>> So obviously those keepalive packets do not reset the timeout >>>> (where ever it happens) however sending some bytes may help, see >>>> above. >>>> >>> >>> Try sending the NOOP command periodically whilst >>> downloading/uploading. Most servers should support this. >>> Not sure >>> how the component will handle the response if it's waiting for the >>> response from the GET/PUT though. >> >> You are right! >> A response to a NOOP before GET/PUT finished would kill a transfer. >> However some (most?) servers queue client requests, the NOOP >> responses would the be received after the transfer completed. ICS >> FTP server does not queue requests. > > In my experience, most FTP servers treat a NOOP in a special way and > will process it and reply even during a transfer. It's worth a try.
If they reply at once the client would treat the NOOP-response as an response to GET/PUT, thus data socket will be closed, see procedure TCustomFtpCli.Next2GetAsync. The FTP server of my ISP however doesn't reply until PUT/GET completed, just tested. Instead, after the download succeeded I was bombed with plenty of NOOP-responses. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- 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
