15.1. Basic RMI Concepts
So, you have an object on System A, and would like to call some method in another object on System B. Obviously, there's going to be some network calls involved in this process. Without RMI, you'd be making those network calls yourself. With RMI, the actual network code is provided for you. In a RMI application, the remotely accessible object is shadowed by two new objects that provide this networking code. On the server side, the code is called a skeleton; on the client side, it is called a stub. The stubs and skeletons are theoretically there to isolate your code from the network, yet in a completely unsatisfying way that forces you to nevertheless remain constantly aware of when an object is local and when it is remote, ...
Get J2EE™ and JAX™: Developing Web Applications and Web Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
