🚀 go-pugleaf

"Hanne B" <hb@aeromark.dk> wrote in message
news:4552e3ba$1@newsgroups.borland.com...

> If they are interrupted while they are retrieving files (and I don't get
the
> disconnected event for the client), then they will stay "connected"
> and take up memory

Blocking sockets cannot detect abnormal disconnects in a timely manner.
TIdFTPServer in Indy 9 does not have enough hooks for you to customize the
connection's behavior, such as being able to automate the handling of
reading timouts.  The closest you can get is to set the
CommandHandlersEnabled property to False, then use the OnConnect event to
set the ReadTimeout property on a per-client basis, and then use the
OnExecute event to manually call ReadLn() and check the ReadLnTimedOut
property before then passing the received line to the CommandHandlers for
processing.  If a timeout occurs, you can disconnect the client.

> What exactly do you want me to do to disconnect the DataChannel first ?

TIdFTPServerThread has a DataChannelThread property.  Unfortunately, you do
not have access to the socket that it creates to transfer the data.  You
would have to change Indy's source and then recompile Indy in order to do
that.  Then you can disconnect the socket when needed, which will
effectively abort the transfer.

> how do I send an error message to the FTP client ?

TIdFTPServer automatically does that when the transfer thread fails to
transmit/receive data.


Gambit