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 :-(
Le 20 juin 08 à 16:44, Bernard Devlin a écrit :
Happy to help if I can. I have a Netgear router here, but for my
test I
just switched off the wireless adaptor on my laptop to break the
network
connection. So, this time I switched off the router. Now I get a
14 second
delay before rev times out. When I ran nslookup.exe on Windows in
this
situation, it only takes 2 seconds to report it can't resolve the
address.
Perhaps you might have to use shell() to call nslookup.exe and
check what
that returns. Also, since it doesn't look like Rev is making the
same call
that nslookup.exe makes, maybe it is connected to the
SocketTimeoutInterval
which defaults to 10 seconds?
Bernard
On Fri, Jun 20, 2008 at 2:19 PM, Eric Chatonet <
[EMAIL PROTECTED]> wrote:
Bonjour Bernard,
Thanks for your quick test :-)
But may be I was not specific enough:
Here I have a Netgear router that allows me to share Internet
connection
between several hard wired computers.
Probably it has something to do with this...
On the other hand I use the same Home Premium Vista version than you.
Internet check is always something tricky because of firewalls,
routers,
etc.
Well: why Rev that provides revBrowser does not provide a built-in
function?
:-(
Best regards from Paris,
Eric Chatonet.
----------------------------------------------------------------
Plugins and tutorials for Revolution: http://www.sosmartsoftware.com/
Email: [EMAIL PROTECTED]/
----------------------------------------------------------------
_______________________________________________
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
