I done some further tests, and mostly I'm getting a result with the router disconnected of less than 30ms now. I can't reproduce the case where I got 14 seconds. I had a look at socketTimeoutInterval and it seemed to make no difference at all. Still, if you are getting lengthy delays then it looks like this is not an adequate way to get a speedy test to see if the internet connection is still alive.
Bernard On Fri, Jun 20, 2008 at 3:53 PM, Eric Chatonet < [EMAIL PROTECTED]> wrote: > Your allusion about SocketTimeoutInterval seems to be very well thought :-) > The problem is that I (the user) can't accept more than a 200 ms hang and > this could be not enough when he is regularly connected. > So this fails to address the problem :-( > > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
