Well the use case differences are obvious, but to say the obvious
I am connecting with
a) our own server
b) YouTube
that’s it.
AND I want to know if the URL in the app is correct (silly typo in a JSON in
the app OR misfiled media on out server...etc), so I would always to get the
header of the actual media being called. We can traps errors, send to the
MotherShip the URL that failed and fix it... etc.
That different from (Klaus's ?) "am I connected or not"
BR
On 7/27/18, 12:44 PM, "use-livecode on behalf of Mark Wieder via use-livecode"
<use-livecode-boun...@lists.runrev.com on behalf of
use-livecode@lists.runrev.com> wrote:
> if (tResult < 400) then
> return true
> else
> return false
> end if
I'd be a little wary of that "< 400" result though. You may (or may not)
want to follow redirects, and if you get a 418 you may want a cuppa <g>.
and due to the extra hops involved, I probably wouldn't try for
"https://www.google.com";. DNS resolution will add tens to over a hundred
milliseconds to a web command, so if you're going to go that route
instead of opening a socket I'd go straight to "http://8.8.8.8:53";.
curl -v --trace-time 8.8.8.8:53
20 milliseconds
curl -v --trace-time www.google.com
50 milliseconds
But otherwise, yes... there is no way of checking for the internet
without connecting to the internet.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
