Activatable Remote Objects

Before Java 2, the UnicastRemoteObject could be accessed only from a server program that created instances of the object and ran all the time.
With Java 2 we got the Activatable and the rmid daemon.
An activatable class needs only to be registered with the rmid.
This is an advantage for systems that have many remote object classes but only a few of them are active at any one time. They save memory (and so gain performance).