> Is there a special reason why methods ConnectFeatAsync and
> ConnectFeatHostAsync are not executed with their own request types?
>
> {* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * * * * *}
> procedure TCustomFtpCli.ConnectFeatAsync; { V7.09 }
> begin
> HighLevelAsync(ftpConnectAsync, // <= ftpConnectFeatAsync ?
> [ftpFctOpen, ftpFctAuth, ftpFctUser, ftpFctPass,
> ftpFctAcct, ftpFctFeat]);
> end;
Simplicity perhaps, and backward compatibility.
These were new methods since ftpConnectAsync used to do FEAT but was
causing problems with some old servers that could not cope with the
command, so FEAT was removed and got it's own method.
Adding ftpConnectFeatAsync would not mess up any of my applications.
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
