Advertisement

Reliable Remote Procedure Calls (Extended Abstract)

  • S. K. Shrivastava
Conference paper
Part of the Informatik-Fachberichte book series (INFORMATIK, volume 83)

Abstract

A very convenient means of arranging communication between ‘client’ and ‘server’ processes in a distributed system is to make use of Remote Procedure Calls (RPC’s) enabling clients to invoke services offered by remote servers and obtain appropriate results. Conceptually, a very simple client-server protocol is needed to implement an RPC mechanism: the client sends its service request as a ‘call’ message to the server, and waits for a reply; the server on the other hand receives the ‘call’ message, performs the service and sends the result as a ‘reply’ message to the client. Despite the apparent simplicity of such a protocol, a number of reliability issues are involved that require careful analysis during the design phase. This paper briefly reviews work done at Newcastle in this area, details of which can be found in [Pan82, Shr82, Shr83, Shr84].

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [Bog80].
    Boggs, D.R., J.F. Shoch, E.A. Taft, and R.M. Metcalfe, “Pup: An Internetwork Architecture”, IEEE Trans. on Communications Vol. COM-28(4), pp.612–624 (April 1980).CrossRefGoogle Scholar
  2. [Lar83].
    Larus, J.R·, “On the Performance of Courier Remote Procedure Calls under 4.1c BSD”, UCB/CSD 83/123, EECS CSD University of California, Berkeley (August 1983).Google Scholar
  3. [Mit82].
    Mitchell, J.G. and J. Dion, “A Comparison of Two Network-Based Pile Servers”, CACM Vol. 25(4), pp.233–245 (April 1982).Google Scholar
  4. [Nel81].
    Nelson, B.J., “Remote Procedure Call”, CMU-CS-81–119, Dept. Computer Science, Carnegie-Mellon University, Pittsburgh, PA (1981).Google Scholar
  5. [Pan82].
    Panzieri, F. and S.K. Shrivastava, “Reliable Remote Calls for Distributed Unix: An Implementation Study”, Proc. 2nd Symp. on Reliability in Distributed Software and Database Systems, Pittsburgh, PA. pp.127–133, IEEE Computer Society (July 1982).Google Scholar
  6. [Ryb82].
    Rybczynski, A., “Packet Switched Network Layer”, p. Plenum Press in Computer Network Architectures and Protocols, ed. P.E. Green, Jn., New York (1982).Google Scholar
  7. [Shr82].
    Shrivastava, S.K. and F. Panzieri, “The Design of a Reliable Remote Procedure Call Mechanism”, IEEE Trans. on Computers Vol. C-31(7), pp.692–697 (July 1982).CrossRefGoogle Scholar
  8. [Shr83]·
    Shrivastava, S.K., “On the Treatment of Orphans in a Distributed System”, Proc. 3rd Symp. on Reliability in Distributed Software and Database Systems, Adam’s Mark Caribbean Gulf Resort, Clearwater Beach, Florida, pp.155–162, IEEE Computer Society (October 1983).Google Scholar
  9. [Shr84].
    Shrivastava, S.K., “Semantics, Exception Handling and Orphan-Treatment for Remote Procedure Calls”, Tech. Report, University of Newcastle upon Tÿne (1984).Google Scholar
  10. [Sun78].
    Sunshine, C.A. and Y.K. Dalai, “Connection Management in Transport Protocols”, Computer Networks Vol. 2, pp.454–473, North-Holland Publishing Company (1978).Google Scholar
  11. [Wil79]·
    Wilkes, M.V. and D.J. Wheeler, “The Cambridge Communication Ring”, Proc. Local Area Network Symp., Boston, National Bureau of Standard (May 1979).Google Scholar
  12. [Xer8l].
    Xerox, “Couriers The Remote Procedure Call Protocol”, XSIS 038112, Xerox Corporation, Stamford, Connecticut (December 1981).Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1984

Authors and Affiliations

  • S. K. Shrivastava
    • 1
  1. 1.Computing LaboratoryThe University of Newcastle upon TyneNewcastle upon TyneUK

Personalised recommendations