Re: Detecting server on lan

From:

Nigel Wade <nmw@ion.le.ac.uk>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 03 Jul 2009 17:46:05 +0100

Message-ID:

<h2lcke$b80$1@south.jnrs.ja.net>

Michal Kleczek wrote:

Nigel Wade wrote:

Tom Anderson wrote:

On Thu, 2 Jul 2009, Lew wrote:

Ken T. wrote:

You still have to have its IP address and my clients aren't running an
RMI
registry now on any machine. At their site there is no standard
location for the RMI registry.
Maybe I'm missing something. Is there a way to locate the RMI registry
on the local area network?

When you run the registry, you will know on which machine you ran it.

The WHOLE POINT of this thread is that the machines which need to find
the registry DO NOT know which machine it was run on!

But the WHOLE POINT rmiregistry, and network and server administration in
general, is that the clients SHOULD KNOW.

Why?

Because you end up with a simple, working, solution in a matter of minutes. It's
easy to understand and easy to configure and maintain. If it's a small network
then a simple solution is probably going to be the best option. The main
question is does the OP need anything more complicated?

Ever heard of ad-hoc networking, service discovery, randezvous, mdns, jini
etc. etc.?

If the OP has the programming/technical resources necessary to implement one of
the above approaches then fine, let them go ahead and do so. All you need to do
is tell them how.

The problem the OP has could be solved by using rmiregistry on a known server.
It's only one solution, it may not be acceptable to the OP (I don't know that),
but it *is* a solution, and a very simple one.

--
Nigel Wade