> Back to implementation, is there a way to do these steps: > 1. Periodically check the state of TWSocket > 2. If it is not listening, put it to listen again > 3. If no response from TWSocket, destroy it and create a new instance
You can have one TWSocket connect to another one within the same application. Just use a TTimer to do it periodically. If it is no listening anymore but you have not closed it, then there is a bug somewhere ! You should instrument your application to know what happend. It is likely the OS is out of resource, probably because there is a leak somewhere. Very difficult to find actually. Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
