I just ran into a situation I thought I was covering. Some of my applications have version check code that uses a HTTPSocket to fetch a small file from the Web that contains the latest version number. Before using the Get method on the HTTPSocket, I check its localAddress property to see if it has an IP address. I thought this was protecting against downed connections. But tonight my DSL modem crapped out temporarily, and my application locked up because the socket was still reporting a valid IP address and the code proceded to calling the HTTPSocket.Get method.
Is that expected behavior? If so, is there any other way to work around it? Can I set a timeout on the socket so that such a lockup would be reasonably brief? I discovered this in RB 2006r3 under Mac OS X 10.4.7. _______________________________________________ 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>
