To avoid this problem, I must make a 1 second pause and processmessages
before launch a new connection.
The MakePause procedure is like:
FTPClient.ProcessMessages()
intFinish = Timer + 1
Do While Timer intTempsFinal
Loop
FTPClient.ProcessMessages()
Arnold FLUTEAUX wrote:
Hello,
Sorry but I've always my problem.
I launch a GET and I kill the client connection on my FTP server.
Then, I launch a new connection and I've an error which triggers in
the OnError : FTP already connected. And in
overbite.ICS.ftpclient.pas there is this
Arnold FLUTEAUX wrote:
Thanks for your response.
I test it but when I cut on the connection with server during a
download, a requestdone triggers but not the sessionclosed.
Event OnSessionClosed is only triggered when the control connection
closes. When data connection closes only
Indeed, Requestdone triggers but once time, the connected property is set to
true.
If I try to launch again a getasync command without reconnection, at this
time I have an error and the Connected property is set to False.
And side server, I launch FTPServer.disconnect property and the client is
Arnold FLUTEAUX wrote:
Indeed, Requestdone triggers but once time, the connected property is
set to true.
If I try to launch again a getasync command without reconnection, at
this time I have an error and the Connected property is set to False.
And side server, I launch FTPServer.disconnect
If I understand well what you say, in may case, when I cut off voluntarily
the connection from server side, the datasocket must be closed and the
Connected property must be True. Is that ?
What I don't understand is :
-if I launch a quitAsync = I've FTP Component not connected. And if
I
Arnold FLUTEAUX wrote:
If I understand well what you say, in may case, when I cut off
voluntarily the connection from server side, the datasocket must be
closed and the Connected property must be True. Is that ?
The order in which both connections are closed determines the
server, it may be
I cut off the server, then an error product in RequesDone with ErrCode 0.
Its OK. So Ive made a procedure to analyze the error and I test the
connected property and the controlsocket.state property and it says that
the winsock is already connected. In debug mode, it says the same except if
To launch a new connection is not a problem. But to launch it, I must know
if the winsock is deconnected or no.
If winsock is always connected then I try again to launch the command which
has had a problem and if winsock is disconnected, I launch a new connection
in other procedure than
Of Arnold FLUTEAUX
Sent: 11 July 2006 08:50
To: twsocket@elists.org
Subject: Re: [twsocket] Problem with FTPClient when a shutdown
To launch a new connection is not a problem. But to launch it, I must know
if the winsock is deconnected or no.
If winsock is always connected then I try again to launch
Message-
From: [EMAIL PROTECTED] [mailto:twsocket-
[EMAIL PROTECTED] On
Behalf Of Arnold FLUTEAUX
Sent: 11 July 2006 08:50
To: twsocket@elists.org
Subject: Re: [twsocket] Problem with FTPClient when a shutdown
To launch a new connection is not a problem. But to launch it, I must
know
OK I havn't explain very well my problem.
I don't have unplugged the network cable, I cut off the client connection on
my FTP server.
Then an error is triggered in RequestDone with an error. And I know that
there is a disconnection because I kill the client connection but Connected
property is
OK my problem seems to be solve. Connected property is set to true,
controlsocket.state is not set to wsclosed but datasocket.state is set to
wsclosed so I test also this property to know if I must launch a new
connection.
Thanks for your help.
Arnold
--
To unsubscribe or change your
13 matches
Mail list logo
