NOOP is a good one.
Dan
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Monday, May 16, 2005 2:44 PM
Subject: Re: [twsocket] Disconnect from FTP Server [FTP Client]
>Winsock nor the component will let you
doesn't know the
command !
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Artem Antonov" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Monday, May 16, 2005 4:43 PM
Subject: Re: [twsocket] Disconnect from FTP Server [FTP Clie
On Mon, 16 May 2005 15:44:25 +0200
"Francois PIETTE" <[EMAIL PROTECTED]> wrote:
Any command that do the less possible processing on the server. PWD
and SYST
are probably the best choices. SYST is not implemented on all
servers.
Probably sending an invalid command could also be good, just to
rec
> >Winsock nor the component will let you know the server disconnected
> >before you try to send something. So the solution is to periodically send
a
> >command just to get the error in case the server closed the connection.
Note
> >that periodically sending a command will probably prevent the serv
On Mon, 16 May 2005 14:46:27 +0200
"Francois PIETTE" <[EMAIL PROTECTED]> wrote:
Winsock nor the component will let you know the server disconnected
before you try to send something. So the solution is to periodically send a
command just to get the error in case the server closed the connection.
> 1) Client connects to the FTP server
> 2) After timeout or in the case of connection error FTP server close
> connection
> 3) FTP client recieve (immediately) message that FTP server is not
> avialable
> 4) Other actions on the side of client
>
> How I can realaize the 3) step?
> Does anybody sol
Hello,
I've already written in this maling list about disconnect from FTP
server in the case when FTP server close connection (how I can control
this event to disconnect client immediately). Sorry, but I can't
solving this problem, so I ask help again.
The steps are:
1) Client connects to the F
