"Guillem" <guillemvicens-nospam@clubgreenoasis.com> wrote in message
news:xn0eq8oqwfechw004@newsgroups.borland.com...
> i'm not an expert but this has something to do with the way Windows
> handles the sockets. AFAIK there is no realistic way for you to know if
> a connection has been lost or closed unless you use timeouts or try to
> connect/disconnect.
Hi Guillem, thanks for the reply.
Well it must be the way Windows does it because I can reset the connection
to a Linux server without any problems. I have the following setup:
Linux Server <=> Windows Server <=> Windows Clients (Indy used in the
Windows server and client) the windows server app has a listener and the
client app has a listener just as the windows server.
When the connection goes down on the Linux Server I can recover gracefully
on the windows server and reconnect without restarting the app. But when the
windows server goes down I have to restart the app.
> If you haven't I would suggest to wrap your connect/disconnect in a
> try..finally clause
True I have it in a try except but it only helps me detecting it but I cant
recover from it except to inform the user to close the app and start it
again, and they dont like that idea very much..
Aaaaahhhh Windows!!!
