D
Dido Sevilla
Is there a way to let a method called via druby over TCP/IP learn the
IP address of the remote peer invoking it? If not, is there a way to
allow a local node to obtain its own IP address? I'm writing a program
that involves having clients connect to a server and register
addresses where they can be contacted via druby whenever asynchronous
events later occur. They will then get called by the server when the
asynchronous event occurs. DRb.uri gives useless results for this
application because DRb seems to always use the machine's actual
hostname in the URI, which usually doesn't resolve because many of
the clients have dynamic IP's and don't have valid hostnames as such,
especially the Windows boxes which run the client.
IP address of the remote peer invoking it? If not, is there a way to
allow a local node to obtain its own IP address? I'm writing a program
that involves having clients connect to a server and register
addresses where they can be contacted via druby whenever asynchronous
events later occur. They will then get called by the server when the
asynchronous event occurs. DRb.uri gives useless results for this
application because DRb seems to always use the machine's actual
hostname in the URI, which usually doesn't resolve because many of
the clients have dynamic IP's and don't have valid hostnames as such,
especially the Windows boxes which run the client.