comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » socket issue

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: socket issue [message #52716 is a reply to message #52605]

Mon, 26 February 2007 05:07

Bringfried Stecklum is currently offline

Bringfried Stecklum
Messages: 75
Registered: January 1996

Member

Dear Nigel,

I am aware of the cause for the error. I also wrote that remotehost can
be resolved and reached ouside of IDL. My point was that IDL could be a
bit more flexible by checking whether the DNS configuration found at
startup is still valid when socket is being called. People move around
with laptops these days and DNS service can change quickly.

regards,

Bringfried

Nigel Wade wrote:
> Bringfried Stecklum wrote:
>
>> One of my programs retrieves data over the web using the socket
>> procedure. It also runs on the laptop which has different network
>> settings depending on where I am. Usually the IDL session is kept
>> running when hibernating/resuming the system. In this case I noticed
>> that socket does not become aware of the change in the network settings
>> and fails
>>
>> % SOCKET: Unable to lookup host. Unit: 1, File: remotehost
>>
>> Of course remotehost can be reached. So it seems that the network
>> configuration is fixed upon IDL startup, and not dynamically updated.
>>
>> regards,
>>
>> Bringfried Stecklum
>
> "Unable to lookup host." looks like a failure in DNS hostname resolution. What
> host is it trying to connect to, and can you resolve that hostname outside of
> IDL?
>

Report message to a moderator

[Message index]

		socket issue By: Bringfried Stecklum on Thu, 22 February 2007 01:30
		Re: socket issue By: Bringfried Stecklum on Mon, 26 February 2007 05:07
		Re: socket issue By: Nigel Wade on Fri, 23 February 2007 02:36

Previous Topic:	find index
Next Topic:	Re: find index

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Dec 02 22:30:24 PST 2025

Total time taken to generate the page: 1.99768 seconds