Dan wrote:
> I've had servers that take slightly more than 60 seconds to establish the
> connection, but once connected they work fine (no lag). 

OK, the best would be to deligate timeout setting to the user,
as Wilfried wrote. 

> maybe its only possible for
> blocking sockets,
I don't think so, since I'm running a non-blocking mail server that provides
user defined TCP timeout settings as well. 

> but someone could check their sourcecode and see what
> they do.

I'll have a look at it.

Arno Garrels

> ----- 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

Reply via email to