RMI Stubs and Skeletons

Remote clients communicate with server objects via stubs and skeletons.    These stubs and skeletons are produced by running RMIC on class files that extend UnicastRemoteObject and have an interface that extends Remote.

• The stubs and skeletons are adapters that first adapt the client to the Internet and then the Internet to the server's object.
• Any serializable object (i.e. implements Serializable) can be transmitted to the server by use of an input parameter if a method of the IRemoteObject interface.
• Any serializable object can be sent to the client by use of the return value of a method of the IRemoteObject interface.
• Any method that the client runs on the remote object actually runs on the server.
• Any method of a serializable, non-UnicastRemoteObject object set to the client runs on the client.
•  A class server must be running in order for the RMIRegistry to initially load the stubs in preparation for transmitting them to clients.