J. Waldo. Remote procedure calls and java remote method invocation. IEEE Concurrency, 6(3):5--7, 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....some programming model for which an Ibis version exists. At this moment, we have implemented four runtime systems for programming models on top of the IPL: RMI, GMI, RepMI and Satin. RMI is Java s equivalent of RPC. However, RMI is object oriented and more flexible, as it supports polymorphism [32]. In [26] we demonstrated that parallel grid applications can be written with RMI. However, application specific wide area optimizations are needed. GMI [22] extends RMI with group communication. GMI also uses an object oriented programming model, and cleanly integrates into Java, as opposed to ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July 1998.

....generating specialized serialization routines during compile time, by reimplementing the RMI protocol it self, and by using LFC and Panda instead of TCP IP. Manta uses its own RMI protocol, but also has the functionality to interoperate with other Java Virtual Machines. To handle polymorphic RMIs [53], Manta is able to accept a Java class file (bytecode) from a JVM, compile it dynamically to a binary format, and link the result into the running application program. We have also developed a fine grained Distributed Shared Memory system for Java, called Jackal [52] Jackal allows multithreaded ....

J. Waldo. Remote Procedure Calls and Java Remote Method Invocation. IEEE Concurrency, pages 5-7, July-September 1998. 2O

.... different forms of object replication have been proposed for Java [9, 14, 19, 25, 27] no scheme exists yet that transparently and efficiently supports replicated objects in Java and that integrates cleanly with Java s primary point to point communication mechanism, Remote Method Invocation (RMI) [28]. Some systems temporarily cache objects rather than trying to keep multiple copies of an object consistent [9, 14, 19, 27] Some proposals have a programming model that is quite different from the object invocation model of RMI [25] Also, performance results are often lacking or disappointing. ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, 6(3):5--7, July--September 1998.

....the same time, a certain amount of functionality has to be replicated, since it has to be available at both communication partners, which makes maintenance harder. For these reason the required commonalties between the platforms should be kept as small as possible. Java Remote Method Invocation [10] is an interesting combination of code reuse and service reuse. It is a language specific remote procedure call mechanism and it can automatically load code that is not available at the destination of a call, but is necessary to execute the call. This typically happens when the call has parameters ....

Waldo, J. Remote Procedure Calls and Java Remote Method Invocation. IEEE Concurrency 6, 3 (1998), 5-7.

....The processes of this application use Manta s fast RMI protocol to communicate with each other. They can also communicate with applications that run on standard JVMs using the standard RMI protocol. They can even exchange bytecode with these applications, which is required for polymorphic RMIs [11]. For this purpose, the Manta compiler also generates bytecode for Java programs (which can be sent to remote JVMs) and the Manta runtime system contains a compiler to process incoming bytecode from a JVM. The net result is that Manta provides efficient sequential code, fast communication, ....

J. Waldo. Remote Procedure Calls and Java Remote Method Invocation. IEEE Concurrency, 6(3):5--7, July--September 1998.

....never changes, and, in particular, that it is location independent. In contrast, a (location dependent) contact address is used to refer to the current location of an object. As we explained, a contact address in CORE is implemented as a serialized proxy, similar to the use of proxies in Java RMI [22]. When a client wants to bind to an object it looks up the object s current location by providing the object identifier to the location service. The location service returns a contact address in the form of a serialized proxy. This proxy is subsequently deserialized by the client and automatically ....

.... There are only a few distributed object models that follow this approach, notably the fragmented objects as developed by the SOR group at INRIA [10] At best, support is given for adapting the client proxy to specific objects, as used in Spring s subcontract model [5] or as implemented in Java RMI [22]. To compensate for the lack of flexibility in the supported object model, CORBA provides interceptors as a mechanism to provide object specific policies [11] However, interceptors essentially allow only breaking into an existing ORB and modifying its invocation policy. Much more is needed to ....

J. Waldo. "Remote Procedure Calls and Java Remote Method Invocation." IEEE Concurrency, 6(3):5--7, July 1998.

....growing interest in using Java for high performance applications. Among other needs, these applications frequently demand a parallel computing infrastructure. Although Java offers appropriate mechanisms to implement Internet scale client server applications, Java s remote method invocation (RMI, [23]) is too slow for environments with low latency and high bandwidth networks, e.g. clusters of workstations, IBM SP 2, and SGI Origin. 1.1 Breakdown of RMI cost We have studied the cost of a remote method invocation on two platforms: two PCs: 350 MHz Pentium II, running Windows NT 4.0 ....

....packet checksums is better done in hardware. If the network does not drop any packets, there is no need to implement acknowledgement in software. Thus, any portable RPC design must allow to use platform specific and optimized transport layer implementations. RMI extends the ideas of RPC to Java [23]. In contrast to earlier RPC systems, RMI is designed for a single language environment, where both caller and callee are implemented in Java. The two most essential differences are that RMI enables the programmer to use a global object model with a distributed garbage collector. Second, ....

Jim Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, 6(3):5--7, July--September 1998.

.... different forms of object replication have been proposed for Java [12, 18, 24, 32, 35] no scheme exists yet that transparently and efficiently supports replicated objects in Java and that integrates cleanly with Java s primary point to point communication mechanism, Remote Method Invocation (RMI) [36]. Some systems temporarily cache objects rather than trying to keep multiple copies of an object consistent [12, 18, 24, 35] Some proposals have a programming model that is quite different from the object invocation model of RMI [32] Also, performance results are often lacking or disappointing. ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July--September 1998.

....The processes of this application use Manta s fast RMI protocol to communicate with each other. They can also communicate with applications that run on standard JVMs using the standard RMI protocol. They can even exchange bytecode with these applications, which is required for polymorphic RMIs [11]. For this purpose, the Manta compiler also generates bytecodes for Java programs (which can be sent to remote JVMs) and the Manta runtime system contains a compiler to process incoming bytecodes from a JVM. The net result thus is that Manta provides efficient sequential code, fast communication, ....

J. Waldo. Remote Procedure Calls and Java Remote Method Invocation. IEEE Concurrency, 6(3):5--7, July--September 1998.

.... different forms of object replication have been proposed for Java [12, 18, 24, 32, 35] no scheme exists yet that transparently and efficiently supports replicated objects in Java and that integrates cleanly with Java s primary point to point communication mechanism, Remote Method Invocation (RMI) [36]. Some systems temporarily cache objects rather than trying to keep multiple copies of an object consistent [12, 18, 24, 35] Some proposals have a programming model that is quite different from the object invocation model of RMI [32] Also, performance results are often lacking or disappointing. ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, 6(3):5--7, July--September 1998.

....generating specialized serialization routines during compile time, by reimplementing the RMI protocol itself, and by using LFC and Panda instead of TCP IP. Manta uses its own RMI protocol, but also has the functionality to interoperate with other Java Virtual Machines. To handle polymorphic RMIs [53], Manta is able to accept a Java class le (bytecode) from a JVM, compile it dynamically to a binary format, and link the result into the running application program. We have also developed a ne grained Distributed Shared Memory system for Java, called Jackal [52] Jackal allows multithreaded ....

J. Waldo. Remote Procedure Calls and Java Remote Method Invocation. IEEE Concurrency, pages 5-7, July{September 1998. 20

....parameters in a spawned call to a remote machine will not be available on that machine. Therefore, Satin uses call by value semantics when the runtime system decides that the method will be spawned remotely. This is semantically similar to the standard Java Remote Method Invocation (RMI) mechanism [17]. Call by value is implemented using Java s serialization mechanism, which provides a deep copy of the serialized objects [16] For instance, when the rst node of a linked list is passed as an argument to a spawned method invocation (or a RMI) the entire list is copied. It is important to ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5-7, July{September 1998.

.... workstations, Java provides Remote Method Invocation (RMI) which is an object oriented version of Remote Procedure Call (RPC) The RMI model offers many advantages for parallel and distributed programming, including a seamless integration with Java s object model, heterogeneity, and flexibility [Waldo 1998]. Unfortunately, many existing Java implementations have inferior performance of both sequential code and communication primitives, which is a serious disadvantage for highperformance computing. Much effort is being invested in improving sequential code performance by replacing the original ....

....subclass) should be used by the method, not the static type of the formal parameter. When the subclass is not yet known to the receiver, it has to be fetched from a file or HTTP server and be downloaded into the receiver. This high level of flexibility is the key distinction between RMI and RPC [Waldo 1998]. RPC systems simply use the static type of the formal parameter (thereby type converting the actual parameter) and thus lack support for polymorphism and break the object oriented model. The key problem is to obtain the efficiency of RPCs and the flexibility of Java s RMI. This paper discusses ....

WALDO, J. 1998. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency 6, 3 (July--September), 5--7.

....RMI protocol. Thus, two Manta nodes communicate through Manta s own fast RMI protocol, while communication with non Manta JVMs follows the standard protocol. A related problem is that Manta nodes must be able to exchange byte codes with other Java nodes, because RMIs in Java are polymorphic [23]. The parameters or result value of an RMI may be 3 of a subclass of the class specified in the declaration, and this subclass may not yet be present at the sending or receiving machine. To support polymorphic RMIs, Manta is able to accept byte codes from JVMs; this byte code is compiled during ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July--September 1998.

....objects passed as parameters to a spawned call will not be available on the remote CPU. Therefore, Satin uses call byvalue semantics when the runtime system decides that the method will be spawned remotely. This is semantically similar to the standard Java Remote Method Invocation (RMI) mechanism [22]. Call by value is implemented using Java s serialization mechanism, which provides a deep copy of the serialized objects [20] For instance, when the first node of a linked list is passed as an argument to a spawned method invocation (or a RMI) the entire list is copied. It is important to ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July-- September 1998.

.... different forms of object replication have been proposed for Java [8, 11, 15, 20, 22] no scheme exists yet that transparently and efficiently supports replicated objects in Java and that integrates cleanly with Java s primary point to point communication mechanism, Remote Method Invocation (RMI) [23]. Some systems temporarily cache objects rather than trying to keep multiple copies of an object consistent [8, 11, 15, 22] Some proposals have a programming model that is quite different from the object invocation model of RMI [20] Also, performance results are often lacking or disappointing. ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July--September 1998.

....disconnected nodes, or network partitioning. To deal with those kinds of challenging network problems, in general complicated acknowledgement schemes have been designed that unfortunately require additional messages on the critical path of a remote call. Java s RMI (remote method invocation, [12, 14]) uses such a DGC that is suitable for wide area TCP IP networks. However, the use of distributed Java is not restricted to wide area applications, but there is demand to use Java also for parallel and distributed high performance applications that require special purpose high performance ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, 6(3):5--7, July--September 1998.

....a JDK compliant protocol. Two Manta nodes thus communicate using our fast protocol, while Manta to JVM RMIs use the standard RMI protocol. Another problem concerning interoperability is that Manta uses a native compiler instead of a byte code interpreter (or JIT) Since Java RMIs are polymorphic [35], Manta nodes must be able to 3 send and receive byte codes to interoperate with JVMs. For example, if a remote method expects a parameter of a certain class C, the invoker may send it an object of a subclass of C. This subclass may not yet be available at the receiving Manta node, so its byte ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July--September 1998.

....a JDK compliant protocol. Two Manta nodes thus communicate using our fast protocol, while Manta to JVM RMIs use the standard RMI protocol. Another problem concerning interoperability is that Manta uses a native compiler instead of a byte code interpreter (or JIT) Since Java RMIs are polymorphic [35], Manta nodes must be able to send and receive byte codes to interoperate with JVMs. For example, if a remote method expects a parameter of a certain class C, the invoker may send it an object of a subclass of C. This subclass may not yet be available at the receiving Manta node, so its byte code ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July--September 1998.

....RMI protocol. Thus, two Manta nodes communicate through Manta s own fast RMI protocol, while communication with non Manta JVMs follows the standard protocol. A related problem is that Manta nodes must be able to exchange byte codes with other Java nodes, because RMIs in Java are polymorphic [16]. The parameters or result value of an RMI may be of a subclass of the class specified in the declaration, and this subclass may not yet be present at the sending or receiving machine. To support polymorphic RMIs, Manta is able to accept byte codes from JVMs; this byte code is compiled during ....

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July--September 1998.

No context found.

J. Waldo. Remote procedure calls and java remote method invocation. IEEE Concurrency, 6(3):5--7, 1998.

No context found.

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, 6(3):5--7, July--September 1998.

No context found.

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July 1998.

No context found.

J. Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, pages 5--7, July 1998.

No context found.

Jim Waldo. Remote procedure calls and Java Remote Method Invocation. IEEE Concurrency, 6#3#:5#7, July#September 1998.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC