ACM Home Page
Please provide us with feedback. Feedback
A survey of asynchronous remote procedure calls
Full text PdfPdf (911 KB)
Source ACM SIGOPS Operating Systems Review archive
Volume 26 ,  Issue 2  (April 1992) table of contents
Pages: 92 - 109  
Year of Publication: 1992
ISSN:0163-5980
Authors
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 22,   Downloads (12 Months): 96,   Citation Count: 7
Additional Information:

abstract   references   cited by   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/142111.142121
What is a DOI?

ABSTRACT

Remote Procedure Call (RPC) is a popular paradigm for interprocess communication in distributed systems. It is simple, flexible and powerful. However, most of the RPC systems today are synchronous in nature, and hence fail to exploit fully the parallelism inherent in distributed applications. In view of this, various asynchronous RPC systems have been designed and implemented to achieve higher parallelism while retaining the familiarity and simplicity of synchronous RPC. Asynchronous RPC calls do not block the caller (client) and the replies can be received as and when they are needed, thus allowing the client execution to proceed locally in parallel with the callee (server) invocation. Asynchronous RPC calls can be classified into two types depending on whether the calls return a value. Most asynchronous RPC systems only support calls that do not return a value, and few support both classes. In this paper, an analysis and comparison of various asynchronous RPC systems are presented.


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
[Ananda et al. 91] A.L. Ananda, B.H. Tay, and E.K. Koh, "ASTRA - An Asynchronous Remote Procedure Call Facility", Proc of the 11th International Conference on Distributed Computing Systems (ICDCS-11), IEEE, Arlington, Texas, United States, May 20-24, 1991, pp.172-180.
 
2
[Bal et al. 87] Bal, H.E., Renesse, R. van, and Tanenbaum, A.S., "Implementing Distributed Algorithms using Remote Procedure Call", Proc. National Computer Conference, AFIPS, pp. 499-505, 1987.
 
3
4
5
 
6
7
 
8
[Dineen et al. 87] Dineen, T.H., Leach, P.J., Mishkin, N.W., Pato, J.N., and Wyant, G.L., "The Network Computing Architecture and System: An Environment for Developing Distributed Applications", In Proc. of the USENIX Conference (Phoenix, Ariz., June). USENIX Association, Berkeley, Calif., 1987, pp. 385-398.
9
10
 
11
12
 
13
 
14
[Nelson 81] Nelson, B., "Remote Procedure Call", Report CSL-81-9, Xerox Palo Alto Research Center, May 1981.
 
15
 
16
 
17
 
18
[Schantz et al. 86] R. Schantz, R. Thomas and G. Bono, "The Architecture of the CRONUS Distributed Operating System", Proc of 6th International Conference on Distributed Computing System, Cambridge, Massachusetts, May 19-23, 1986, pp. 250-259.
 
19
[Souza and Miller 86] Robert J. Souza and Steven P. Miller, "Unix and Remote Procedure Calls: A Peaceful Coexistence?", Proc of 6th International Conference on Distributed Computing System, Cambridge, Massachusetts, May 19-23, 1986, pp. 268-277.
 
20
[Sechrest 86] Stuart Sechrest, "An Introductory 4.3BSD Interprocess Communication Tutorial", Unix Programmer's Supplementary Documents, Vol. 1 (PS1), 4.3 Berkeley Software Distribution, Computer Systems Research Group, Computer Science Division, Univ. of California, Berkeley, Calif., Apr. 1986.
21
 
22
 
23
24
 
25
[Walker et al. 90] Edward F. Walker, Richard Floyd, and Paul Neves, "Asynchronous Remote Operation Execution in Distributed Systems", Proc. 10th Intl. Conf. on Distributed Computing Systems (ICDCS-10), IEEE, Paris, France, May 28-June 1, 1990, pp. 253-259.
 
26
[Walker 90] Edward F. Walker, Private Communication, Oct. 1990.
 
27
 
28

CITED BY  7

Collaborative Colleagues:
A. L. Ananda: colleagues
B. H. Tay: colleagues
E. K. Koh: colleagues