ACM Home Page
Please provide us with feedback. Feedback
Lazy argument passing in Java RMI
Full text PdfPdf (847 KB)
Source
ACM International Conference Proceeding Series; Vol. 347 archive
Proceedings of the 6th international symposium on Principles and practice of programming in Java table of contents
Modena, Italy
SESSION: Optimization and run-time performance II table of contents
Pages 127-136  
Year of Publication: 2008
ISBN:978-1-60558-223-8
Authors
Christopher Line  Purdue University, West Lafayette
K. R. Jayaram  Purdue University, West Lafayette
Patrick Eugster  Purdue University, West Lafayette
Sponsor
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 67,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1411732.1411750
What is a DOI?

ABSTRACT

Though often criticized for its inherent synchronization overhead and coupling, the remote method invocation (RMI) paradigm remains one of the most popular abstractions for building distributed applications. Many authors have suggested ways to overcome its drawbacks focusing mostly on the invoker's perspective, for example by multiplexing invocations to replicated server objects, through "future" return values, or even by prohibiting return values altogether. The more global perspective, and in particular the invokee side, has conversely only received little attention.

In this paper we take a fresh look at the RMI paradigm, elaborating on argument passing semantics. We identify three lazy ways of passing arguments by value, differing by the moment at which the transfer of the arguments synchronizes with the execution of the method body. We present a preliminary library implementation of our argument passing semantics in Java RMI, and illustrate their individual benefits through examples. We characterize analytically and empirically application scenarios which benefit from lazy argument passing.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
J.-P. Briot. Actalk: A Testbed for Classifying and Designing Actor Languages in the Smalltalk-80 Environment. In Proceedings of the 3rd European Conference on Object-Oriented Programming (ECOOP '89), pages 109--129, July 1989.
 
2
3
4
 
5
 
6
 
7
 
8
R. Friedman and A. Kama. Transparent Fault-tolerant Java Virtual Machine. In Proceedings of the 22nd IEEE Symposium on Reliable Distributed Systems (SRDS '03), pages 319--328, October 2003.
9
10
11
 
12
 
13
 
14
J. Napper, L. Alvisi, and H. Vin. A Fault-tolerant Java Virtual Machine. In Proceedings of the 4th IEEE International Conference on Dependable Systems and Networks (DSN 2003), pages 425--434, June 2003.
 
15
P. Nienaltowski, V. Arslan, and B. Meyer. Concurrent Object-oriented Programming on .NET. IEE Proceedings Software, Special Issue on ROTOR, 150(5):308--314, October 2003.
 
16
OMG. The Common Object Request Broker: Architecture and Specification, version 3.0. OMG, December 2002.
 
17
 
18
Sun. Dynamic Proxy Classes, 1999.
 
19

Collaborative Colleagues:
Christopher Line: colleagues
K. R. Jayaram: colleagues
Patrick Eugster: colleagues