with a ftp client does your connection need to be asynchronous or blocking.
i have it blocking and after i send the pasv command and try to send something such as the list command nothing happens.
with a ftp client does your connection need to be asynchronous or blocking.
i have it blocking and after i send the pasv command and try to send something such as the list command nothing happens.
Last edited by ColdFire; 05-04-2003 at 07:25 PM.
Alright, are you saying any command after PASV is simply not sent (any further command sent to the server has no effect or the send() results in an error) or that nothing is happening after specifically sending the LIST command?
Socket type, asynchronous or otherwise, shouldn't matter if your application is properly receiving data when data arrives.
"Optimal decisions, once made, do not need to be changed." - Robert Sedgewick, Algorithms in C
The PASV command returns sucessful but anything i send after that doesn't seem to do anything, heres what happens.
after passive mode everything seems dead, nothing returns a response from the server, and i've tryed on multiple servers.Creating socket...OK
Resolving host...
USER...
PASS...
Logged In.
200 Type set to A.
227 Entering Passive Mode (65,113,119,132,16,181).
LIST
Sending USER, that works fine, Then PASS fine TYPE fine PASV fine and then nothing.
Last edited by ColdFire; 05-05-2003 at 12:26 PM.
I suspect the client might end to send other commands before LIST.
Kuphryn