Cache - Proposal 2

If the proxy repository uses a cache, no implementation classes must be copied at start-up. If the mobile code requests an implementation class it is stored in the proxy repository and other mobile codes in the neighborhood requesting the same implementation classes can be satisfied by the stored classes in the proxy. If implementation classes are requested, which are not already stored, the proxy repository must contact the central repository to obtain these implementation classes.

In figure a proxy repository on host 5 would load the implementation classes from the central repository when they are requested for the first time from the hosts in neighborhood 2 . The hosts in neighborhood 2 do not see the central repository and direct all requests to the proxy repository.

The connection to the central repository can only be released by the proxy repository under the assumption that the hosts in the neighborhood offer a homogeneous environment to the mobile code. If this assumption is valid, the same implementation classes are requested by a mobile code on all hosts in the neighborhood. After the mobile code has visited the first host and executed its task, all implementations which are needed for the execution of the task are stored in the cache of the proxy repository and further request can be satisfied by the content of the cache.