> So that's the end of it. It's the server that's causing my troubles...
Good to know. > Is it worth using different time-out's for different stages of > connection? Ex: use a long timeout for DNS queryes, use shorter timeout > for the connection itself, use long timeouts for data transmission itself? There is no general rule. It depends on what your application does. I use a simple timout, something like 30". I start the timer before doing anything and then restart it in each step, including when data is received. If the timer triggers, then there was 30" since the last activity, whatever it was. When a timeout is detected, I usually retry 3 times before letting the user know. After 3 retries, I just tell the user something goes wrong and he must try later. I record detailled errors in the log file but I do not bother the user with the details. I just say - like Microsoft - "The service is currently unavailable, try later". -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
