Re: [twsocket] Reasonable timeout

[Dan]

I've had servers that take slightly more than 60 seconds to establish the 
connection, but once connected they work fine (no lag).  It was because it 
was trying to do a reverse dns lookup and there was something wrong with the 
dns coniguration, but still, it can happen.
As for other products overriding the system default, Im not sure, but I 
think Indy can have a user-defined timeout...maybe its only possible for 
blocking sockets, but someone could check their sourcecode and see what they 
do.

Dan
----- Original Message ----- 
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Saturday, April 23, 2005 7:22 AM
Subject: Re: [twsocket] Reasonable timeout

Thanks Wilfried,
...
My opinion was (and still is) that if I don't get a response after
30-50 sec it's useless to wait any longer since either the line is too
bad or a server is too busy to finish a transaction successfully either.
But I'll make it like you said and will satisfy them by a little spinedit
to play with ;)
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