On 9/30/06, Phil M <[EMAIL PROTECTED]> wrote:
Local address is valid any time you are connected to a network. This network does not have to be connected to the internet.
I understand that.
If you want to check and see if you are connected to a Network, then you can use the System.Network.IsConnected( ) method. But like I said, it does not guarantee that the computer is connected to the Internet.
Correct. That doesn't help.
Depending on how you use the HTTPSocket, you should have a Timeout period or you should be using Events. If you have the Timeout period set to zero and the server cannot be found, then your program would lockup indefinitely. While not as convenient, it is better to Subclass the HTTPSocket and use the Events... you will then receive an Error event almost immediately if the computer is not connected to the internet or if your hosting account is unavailable.
I'm using a subclass and I'm using events. And I just discovered the problem thanks to your use of the key word "error". For some reason I had stripped code out of the Error event handler when I made my last "upgrade" to this functionality. It's back now and working properly. So, big thanks for the help. That's why I love this list. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
