15.3. The RMI Registry
In all client-server applications, there must be a way for the client to locate the server to which it will connect. In a typical sockets-based application, this is done by having the server listen on a well-known TCP port number, and the client connects to that port. For many Java architectures, such as JMS or EJB, JNDI is used. With RMI applications, there is an intermediary process known as the rmiregistry. The server object registers itself in the registry using a name, rather than a numeric port number. Clients contact the registry and ask for a server by name. Behind the scenes, all of this is still getting mapped down to port numbers, but it makes it a little easier on the programmer to think in terms of service ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access