The following is a post I made on West-Wind's message board earlier this week. No responses. Would appreciate hearing what others think on the the topic of "detecting internet connections, website availability and setting internet protocol timeouts". My point of reference is using
West-Wind's wwIPstuff product (highly recommended!), but I'm open to any other ideas, products or techniques.
My slightly modified version of my original West-Wind post follows my signature,
Malcolm
I'm looking for some best practice ideas on for detecting internet connection status, website availability, and setting reasonable timeouts for these activities.
This thread was "inspired" by a customer whose ISP recently had DNS problems resulting in my application "freezing" for about 60 seconds when my http code attempted to download a program update from my site.
In reading the West-Wind message boards archives I came across at least 2 techniques for consideration:
1. Using HTTPPing() to determine if my site is accessable
2. Using wwSocket.Connect() and wwSocket.Receive() to determine if my site is accessible;
My thought is that I should be wrapping my application's website access with some sort of "internet connection ok" AND "website ok" status checks AND THEN ... AFTER these status checks have proven successful, use my wwHttp routines to download the files my application is looking for.
So, I'm looking for feedback on:
1. The concept of wrapping wwHttp access with "internet connection" and "website ok" checks - am I being too paranoid or can I acheive the same results by setting wwHttp properties for fast recovery?
2. Technique for determining if an internet connection is present
3. HTTPPing() and/or wwSocket.Connect() or ??? as a technique for verifying that a website is accessable
4. Reasonable timeout values to use for HTTPPing, wwSocket, and wwHTTP activites
West-Wind's wwIPstuff product (highly recommended!), but I'm open to any other ideas, products or techniques.
My slightly modified version of my original West-Wind post follows my signature,
Malcolm
I'm looking for some best practice ideas on for detecting internet connection status, website availability, and setting reasonable timeouts for these activities.
This thread was "inspired" by a customer whose ISP recently had DNS problems resulting in my application "freezing" for about 60 seconds when my http code attempted to download a program update from my site.
In reading the West-Wind message boards archives I came across at least 2 techniques for consideration:
1. Using HTTPPing() to determine if my site is accessable
2. Using wwSocket.Connect() and wwSocket.Receive() to determine if my site is accessible;
My thought is that I should be wrapping my application's website access with some sort of "internet connection ok" AND "website ok" status checks AND THEN ... AFTER these status checks have proven successful, use my wwHttp routines to download the files my application is looking for.
So, I'm looking for feedback on:
1. The concept of wrapping wwHttp access with "internet connection" and "website ok" checks - am I being too paranoid or can I acheive the same results by setting wwHttp properties for fast recovery?
2. Technique for determining if an internet connection is present
3. HTTPPing() and/or wwSocket.Connect() or ??? as a technique for verifying that a website is accessable
4. Reasonable timeout values to use for HTTPPing, wwSocket, and wwHTTP activites