Quote:
Originally posted by robe
it's not fixed in 849 either..
the current behaviour is a violation of the rfc so it can't be right (when there's no transfer running flashfxp "behaves" right, waiting for the 221 response from the server before killing of the control connection).
|
I'll look into that.
Quote:
|
i agree with you that there may be situations where you just want to kill of the data connection (e.g. remote server went dead); what about making the first click on "disconnect" a soft disconnect, and the second abruptively closing the data and control connections?
|
That's exactly how it works. The first click sends QUIT, the second forces disconnect.