Remote Method Invocation (RMI) is available in the current Java language design and implementation, providing the much-needed capability of allowing objects running in different Java processes to collaborate using a variation on the popular Remote Procedure Call (RPC). Although RMI provides features which are desirable for high-performance distributed computing, its design and implementation are deficient in key areas of importance to the high-performance computing community in general. This paper addresses the key deficiencies of RMI and how these deficiencies affect the design and implementation of distributed object applications. Reflective RMI (RRMI) is an open RMI implementation which makes better use of the object-oriented features of Java. RRMI is so-called reflective because it directly employs the reflection capabilities of the current Java language to invoke methods remotely. RRMI makes use of the dynamic class loader (a class called NetClassLoader) to allow client/server applications to be built for high-performance computing systems without having all of the.class files present on all nodes in a parallel computation. Among other features discussed are support for asynchronous remote method invocations with deferred reply and exception semantics.
[1]
Ian T. Foster,et al.
The Nexus Approach to Integrating Multithreading and Communication
,
1996,
J. Parallel Distributed Comput..
[2]
Ian T. Foster,et al.
Managing Multiple Communication Methods in High-Performance Networked Computing Systems
,
1997,
J. Parallel Distributed Comput..
[3]
SkjellumAnthony,et al.
A high-performance, portable implementation of the MPI message passing interface standard
,
1996
.
[4]
Ralph E. Griswold,et al.
The Icon programming language
,
1983
.