The original problem is that the "FTP component not ready" just turns up very occasionally from doing a series of getAsync commands.
So assuming that the error might be from a PORT or PASV, should the sequence of events I take be to call ftp.Abort followed by some sort of restart of my state machine. I assume the FTP component will still be connected or this not necessarily the case. Graham -----Original Message----- From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of Angus Robertson - Magenta Systems Ltd Sent: 10 June 2013 10:31 To: twsocket@lists.elists.org Subject: Re: [twsocket] FTP component not ready > Ok, so what I am trying to establish is that it must be my software > that is causing the problem. I didn't say that, it's probably the control channel dropping, either a network problem or the server disconnecting the session. > There must be some sneaky situation where I am triggering a new > command before the previous one has finished. I said some methods trigger more than one command, the various Connect methods use a sequence of commands, and all upload and download methods do PORT or PASV before GET or PUT. So the not ready error can occur during any of these commands. I'm not sure what your original problem was, error handling is something necessary for all network applications, networks die. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
