Hello Arno, > 2. How can I catch and handle a system TCP timeout in ICS? and
You will get the 10060 (conn timed out) as error argument in the TWSocket events. > 1. How do I find the actual system TCP timeout? Dont know, somewhere in registry I suppose. I _think_ we have a FAQ but I cannot search at moment. > 3. Isn't 30-50 seconds enough even on very bad lines? Should be. However I mostly make it user defined in file | parmeters with a default of 15..60 sec's depending if it is a connection trough LAN - routers between 2 LAN - internet. --- Rgds, Wilfried http://www.mestdagh.biz Friday, April 22, 2005, 20:03, Arno Garrels wrote: > Hello, > Actually I have a custom timeout in all of my applications which > is hardcoded to values between 30-50 seconds. It's that short because > I do not want the system timeout hit in my program flow. > But now users want the timeout user defined and longer :(. > So my questions are: > 1. How do I find the actual system TCP timeout? > 2. How can I catch and handle a system TCP timeout in ICS? and > 3. Isn't 30-50 seconds enough even on very bad lines? > Thanks in advance, > Arno Garrels > -- > 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 -- 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
