|Subject:||Re: TIdFTPServer, Indy 10, ABORting transfers|
|Posted by:||Nicklas Bergfeldt (nicklas.bergfel…@his.se)|
|Date:||Sat, 10 Dec 2005|
It seems like TotalCommander http://www.totalcmd.com) sends an
erroneous ABOR command (it includes some junk-letters):
Of course this is TotalCommander's fault... but the server should not
hang just because the client don't follow the protocol?
I tested with SmartFTP (which sends a correct ABOR command) and that
Hence, it would be great if you could make some sort of idiot-proof
handling of the ABOR command...
... I did that myself in Indy9 where the OnNoCommandHandler was
available, but that's not in Indy10?
- And it also seems like the design has changed so that the loop that
is sending the file is also checking for incomming commands during
Nicklas Bergfeldt wrote:
> I'm using the latest Indy 10 (downloaded just a few hours ago) and have
> a few problems with aborting the data connection...
> First of all, in the simplest case, I want to just abort the transfer
> from the client (TotalCommander) I'm using to connect to Indy... but
> Indy get stuck in an infinite loop in:
> function TIdFTPServer.ReadCommandLine(AContext: TIdContext): string;
> - The server completely halts and won't function any more...
> Then, when the above has been fixed, I would also like to be able to
> abort a transfer from the server side...
> - I cannot find any good methods for achieving that :-(
> Please help me...
> Best regards,
TIdFTPServer, Indy 10, ABORting transfers posted by Nicklas Bergfeldt on Sat, 10 Dec 2005