any way to detect condition "connected to ISP but not internet"?
josh at dvcreators.net
Tue Jan 20 17:05:16 CST 2009
Thanks so much for the input, but the solutions brought up only work
if you are truly NOT connected to your ISP.
The condition I am describing is when you ARE connected successfully
to your ISP, but your ISP is not connected to the internet.
I have not found any way for Revolution to detect this condition, if
you attempt a network operation, it just freezes forever ("beach-
balls"). The timeOutInterval only is functional when there is no ISP
Anyway, if you distribute a commercial app that can operate offline,
make sure it does NOT automatically perform some network operation,
otherwise you might have some angry customers! (who cannot access the
software they paid for!)
We caught this in our own testing before release, so we were lucky.
On Jan 20, 2009, at 8:28 AM, Andre Garzia wrote:
> easiest thing is to ping your own server. Try to load a simple text
> file from your server, if it doesn't load, then, you're not connected.
> For all that matters, this is a good test and easy to implement.
> On Tue, Jan 20, 2009 at 1:11 AM, Josh Mellicker
> <josh at dvcreators.net> wrote:
>> I just thought I'd ask the many networking gurus here:
>> It seems easy with Revolution to check if connected to the
>> internet, if not
>> connected, after a timeOutInterval, an error is returned and it can
>> be dealt
>> with, no problem.
>> Here at our office, we got Time Warner cable internet a few months
>> ago, and
>> while it is speedy (20 mbits d/l!) every few weeks we encounter a
>> and perhaps rare situation where:
>> 1. we are connected to our ISP
>> 2. but our ISP is not connected to the internet
>> On OS X, network diagnostics show:
>> Ethernet = green
>> Network Settings = green
>> ISP = green
>> Internet = red
>> Server = red
>> When we encounter this "false connection" condition, a browser,
>> rather than
>> saying "cannot get web page because we're offline" will hang forever.
>> The danger here that we should all be aware of, is that if you sell
>> an app
>> that, for example, checks for updates upon launch, if your customer
>> has this
>> weird connectivity situation, your app will freeze and the customer
>> unable to get past this and use the app they legitimately paid you
>> Even if the connectivity problem is rare, this is a situation we
>> want to
>> avoid at any cost, so we have no automatic connection routines. If
>> initiate a network operation, and the app hangs, they can force
>> quit and
>> launch again, and not do that anymore now that they know better :-)
>> So, I wondered if any of you had any experience, workarounds or
>> ideas for
>> detecting this "false connection" condition.
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
> http://www.andregarzia.com All We Do Is Code.
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode