"Michael Stieler" <michael.stieler@rie.eu> wrote in message
news:4797088c@newsgroups.borland.com...
> Okay, I was asking because I wanted to make sure there is
> no "cleaner" solution. I agree losing the network cable is not-standard
> but it can happen and I'm surprised that there's no way to do
> a recover.
The OS itself doesn't have any recovery options for abnornal disconnects, so
there is nothing Indy can do on top of that. If the remote machine is lost
and then returns, its local socket stack is going to report errors for any
previous sockets that are no longer valid. The other machines don't know
about the lost until either that machine comes back, or timeouts occur
internally.
Gambit
