Re: Socket timeout not working with libUrl

2005-02-01 Thread Dave Cragg
On 1 Feb 2005, at 01:33, Sarah Reichelt wrote: 2) If I open the socket with a domain address, e.g. www.webphotospro.com, Mac OS X does a DNS lookup, puts up the rainbow rotating color cursor, and hangs until the DNS lookup fails. On my machine this takes 60 seconds (apparently it's

Re: Socket timeout not working with libUrl

2005-02-01 Thread Frank Leahy
at http://www.webphotospro.com/ On Feb 1, 2005, at 4:59 AM, [EMAIL PROTECTED] wrote: From: Sarah Reichelt [EMAIL PROTECTED] Subject: Re: Socket timeout not working with libUrl To: How to use Revolution use-revolution@lists.runrev.com Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset

Re: Socket timeout not working with libUrl

2005-02-01 Thread James Richards
If this is an OS X 10.3.7 issue, some people have been able to kludge a fix for it by entering their ISP's DNS server addresses into the relevant pane in Network preferences. But if it is the identified 10.3.7 problem, you would be likely to have experienced long delays in opening Apple's

Re: Socket timeout not working with libUrl

2005-01-31 Thread Frank Leahy
and Other Photo Power Users See us on the web at http://www.webphotospro.com/ On Jan 31, 2005, at 1:16 AM, [EMAIL PROTECTED] wrote: From: Sarah Reichelt [EMAIL PROTECTED] Subject: Re: Socket timeout not working with libUrl To: How to use Revolution use-revolution@lists.runrev.com Message-ID

Re: Socket timeout not working with libUrl

2005-01-31 Thread Alex Tweedly
Frank Leahy wrote: After a lot of testing on Mac OS X, I've found that the problem I was having appears to be due to the way that Mac OS X does DNS lookups. Whether or not it's a RunRev bug as well is hard to tell, but I think it might be. Here's some sample code I wrote. This code sends a

Re: Socket timeout not working with libUrl

2005-01-31 Thread Alex Tweedly
Alex Tweedly wrote: When you run this script and you're not connected to the internet here's what happens: 1) If I open the socket with an ip address, e.g. 64.125.128.80, my 5 second timer will fire, and I can close the socket and exit from the routine. 2) If I open the socket with a

Re: Socket timeout not working with libUrl

2005-01-31 Thread Sarah Reichelt
2) If I open the socket with a domain address, e.g. www.webphotospro.com, Mac OS X does a DNS lookup, puts up the rainbow rotating color cursor, and hangs until the DNS lookup fails. On my machine this takes 60 seconds (apparently it's dependent on how many dns servers you have listed).

Re: Socket timeout not working with libUrl

2005-01-31 Thread Alex Tweedly
Sarah Reichelt wrote: 2) If I open the socket with a domain address, e.g. www.webphotospro.com, Mac OS X does a DNS lookup, puts up the rainbow rotating color cursor, and hangs until the DNS lookup fails. On my machine this takes 60 seconds (apparently it's dependent on how many dns

Re: Socket timeout not working with libUrl

2005-01-30 Thread Sarah Reichelt
My product pings the Web Photos Pro website to look for new versions. This works great when the computer the product's running on is connected to the internet, but it hangs for 60 seconds when there's no net connection. My code looks like this: set the socketTimeoutInterval to 5000 put

Socket timeout not working with libUrl

2005-01-28 Thread Frank Leahy
Hi, My product pings the Web Photos Pro website to look for new versions. This works great when the computer the product's running on is connected to the internet, but it hangs for 60 seconds when there's no net connection. My code looks like this: set the socketTimeoutInterval to 5000

Re: Socket timeout not working with libUrl

2005-01-28 Thread Alex Tweedly
Frank Leahy wrote: Hi, My product pings the Web Photos Pro website to look for new versions. This works great when the computer the product's running on is connected to the internet, but it hangs for 60 seconds when there's no net connection. My code looks like this: set the