Bernard,
Of course I can't send a GET request (or a LOAD): the software (I
cross my fingers :-) will be used by hundred thousands of persons (I
hope more :-)...
I'll try what I can get from a simple openSocket but I guess that
HostNametoAddress built-in function uses it.
That's the problem...
Le 20 juin 08 à 18:07, Bernard Devlin a écrit :
Maybe the most reliable time-critical way to check would be to open
your own
socket on port 80 to something like www.google.com. By setting the
SocketTimeoutInterval to a low value you would find out quickly if the
timeout occured without a response. I'm thinking that you would
not even
send a GET request, just see if the socket could be opened.
bernard
On Fri, Jun 20, 2008 at 4:52 PM, Eric Chatonet <
[EMAIL PROTECTED]> wrote:
Thanks for testing at your place: it's invaluable :-)
Tests I made were with the router connected but the ADSL modem
disconnected
and I'm afraid it is the delay reason.
Le 20 juin 08 à 17:45, Bernard Devlin a écrit :
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
