Loading…
Asynchronous Remote Method Invocation (ARMI) mechanism for Java
In the recent past, Java has emerged as a powerful and easy to use language for net‐centric computing. Simplicity, object‐oriented features, the presence of threads and architecture independence are the main reasons for the popularity of Java. Despite having built‐in threads in the language, the bar...
Saved in:
Published in: | Concurrency (Chichester, England.) England.), 1997-11, Vol.9 (11), p.1207-1211 |
---|---|
Main Authors: | , , |
Format: | Article |
Language: | English |
Online Access: | Get full text |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Summary: | In the recent past, Java has emerged as a powerful and easy to use language for net‐centric computing. Simplicity, object‐oriented features, the presence of threads and architecture independence are the main reasons for the popularity of Java. Despite having built‐in threads in the language, the bare Java execution model does not support remote object invocations. RMI (remote method invocation) is an interface specified by Sun Microsystems for the purpose of native Java–client and Java–server communication. Although RMI is simple to use, it is not desirable in many applications due to its synchronous nature. In this paper, we describe ARMI (asynchronous RMI), a mechanism which is built on top of RMI and allows concurrent execution of local and remote computations. This paper presents the salient features and implementation details of ARMI. Two experiments performed with ARMI along with performance comparisons to RMI are also explained. © 1997 John Wiley & Sons, Ltd. |
---|---|
ISSN: | 1040-3108 1096-9128 |
DOI: | 10.1002/(SICI)1096-9128(199711)9:11<1207::AID-CPE351>3.0.CO;2-C |