Re: IP # from connection_name?

• Date: Fri, 17 Jan 1997 19:50:16 PST
• From:
  Andrew Wendt <powerpig@m-net.arbornet.org>
• Reply-To:
  Andrew Wendt <powerpig@m-net.arbornet.org>
• cc: moo-calves@ccat.sas.upenn.edu
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <Pine.SOL.3.91.970116190210.22111A-100000@gagarin.cs.Buffalo.EDU>

> > > is there a way to pull the actual connection ip number from one
> > > of the net commands? My connection_name() returns the machine name,
[...]

> Actually, I've seen and worked a little bit with an in-db solution to 
> this...there's an object floating around there called $resolver which has 
> functions that return all that sorta useful stuff, make DNS calls, etc.

I changed my connection_name() to return strings like this:

"port 3200 from localhost (127.0.0.1), port 1032"

This is probably a better solution. The server already hangs looking up the
hostname from the IP when the connection occurs. So it already has the IP and
just doesn't tell it to you. You'd have it hang again waiting for
open_network_connection() with an in-db solution like $resolver. Plus some
hostnames map to multiple IPs so you might not get the IP the connection came
from. It also makes use of the operating system's hostname cache so might
might not need to do a lookup every time.

Although I don't use LambdaCore, I don't think it would break things cuz you
could suitably change $string_utils:connection_hostname_bsd().

Or adding a connection_option() for it wouldn't break anything.

It would be very nice if the server wouldn't hang during name lookups
especially since another process does them anyway. Or if
open_network_connection() could suspend. =8-)

Andy

• Re: IP # from connection_name?
• From: RavenStar <wec@cs.buffalo.edu>

• Prev: Re: IP # from connection_name?
• Next: Re: IP # from connection_name?
• Index: MOO-cows
• Thread: MOO-cows