Socket timeout not working with libUrl

Frank Leahy frank at
Sat Jan 29 05:12:23 EST 2005


Unfortunately there's two types of being "disconnected".  One where 
you've no net connection at all, and one where you're on a LAN, but not 
connected to the Internet.  Here in Cornwall I have only modem access, 
so I've a LAN but no net connection most of the time, which is how I 
stumbled across this problem.

The issue appears to be how Mac OS X does DNS lookups.  The routine 
"lookupd" appears to be the culprit, and RunRev would need to modify 
how they call it to make it non-blocking.

-- Frank

Web Photos Pro: Software for Photo Bloggers and Other Photo Power Users
See us on the web at

On Feb 1, 2005, at 4:59 AM, use-revolution-request at 

> From: Sarah Reichelt <sarahr at>
> Subject: Re: Socket timeout not working with libUrl
> To: How to use Revolution <use-revolution at>
> Message-ID: <c43a037ac64ce0f615b171b9d50db246 at>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>>    2) If I open the socket with a domain address, e.g.
>>, 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).
> What happens if you try:
>    hostNameToAddress("")
> and use the result of that as the address for opening the socket?
> In my tests, this takes about 4 seconds the first time it is called if
> I am connected (which is long enough for the SPOD to appear). When I am
> disconnected, it fails instantly and return empty.
> Sarah

More information about the Use-livecode mailing list