X hits on this document

56 views

0 shares

0 downloads

0 comments

21 / 21

Implementing Remote Procedure Calls

°

59

We believe the parts of our RPC package here discussed are of general interest in several ways. They represent a particular point in the design spectrum of RPC. We believe that we have achieved very good performance without adopting extreme measures, and without sacrificing useful call and parameter semantics. The techniques for managing transport level connections so as to minimize the communication costs and the state that must be maintained by a server are important in our experience of servers dealing with large numbers of users. Our binding semantics are quite powerful, but conceptually simple for a programmer familiar with single machine binding. They were easy and efficient to implement.

REFERENCES

  • 1.

    BIRRELL,A. D., LEVIN,R., NEEDHAM,R. Mo ANDSCHROEDER,M. D. Grapevine: an exercise in distributed computing. Commun. ACM 25, 4 (April 1982), 260-274.

  • 2.

    BOGGS,D. R. Internet Broadcasting. PhD dissertation, Department of Electrical Engineering, Stanford University, Jan. 1982.

  • 3.

    BOGGS, D. R., SHOCH, J. R., TAFT, E. A. AND METCALF, R. M. PUP: An internetwork architecture. IEEE Trans. Commun. 28, 4 (April 1980), 612-634.

  • 4.

    Courier: the remote procedure call protocol. Xerox System Integration Standard XSIS-038112, Xerox Corporation, Stamford, Connecticut, Dec. 1981.

  • 5.

    DATAENCRYPTIONSTANDARD.FIPS Publication 46. National Bureau of Standards, U.S. De- partment of Commerce, Washington D.C., January 1977.

  • 6.

    DEUTSCH,L. P. AND TAFT, E. A. Requirements for an exceptional programming environment. Tech. Rep. CSL-80-10, Xerox Palo Alto Research Center, Palo Alto, Calif., 1980.

  • 7.

    Ethernet, a local area network: data link layer and physical layer specifications version 1.0. Digital Equipment Corporation, Intel Corporation, Xerox Corporation, Sept. 1980.

  • 8.

    LAMPSON,B. W. AND PIER, K. A. A processor for a high-performance personal computer. In Proc 7th IEEE Symposium on Computer Architecture, (May 1980), IEEE, New York, pp. 146-

160.

  • 9.

    LAMPSON,B. W. AND SCHMIDT,E. E.'Practical use of a polymorphic applicative language. In Proc. Tenth Annual ACM Symposium on Principles of Programming Languages (Austin, Texas, Jan. 24-26), ACM, New York (1983), pp. 237-255.

  • 10.

    LISKOV,B. Primitives for distributed computing. Oper. Syst. Rev. 13, 5 {Dec. 1979), 33-42.

  • 11.

    METCALFE,R. M. ANDBOGGS,D. R. Ethernet: Distributed packet switching for local computer networks. Commun. ACM 19, 7 {July 1976), 395-404.

  • 12.

    MITCHELL,J. G., MAYBURY,W. ANDSWEET,R. Mesa language manual (Version 5.0). Tech. Rep. CSL-79-3, Xerox Palo Alto Research Center, Palo Alto, Calif. 1979.

  • 13.

    NELSON,B. J. Remote procedure call. Tech. Rep. CSL-81-9, Xerox Palo Alto Research Center, Palo Alto, Calif. 1981.

  • 14.

    SPECTOR,A. Z. Performing remote operations efficiently on a local computer network. Commun. ACM 25, 4 (April 1982), 246-260.

  • 15.

    WHITE, J. E. A high-level framework for network-based resource sharing. In Proc. National Computer Conference, (June 1976).

Received March 1983; revised November 1983; accepted November 1983

ACMTransactionson ComputerSystems,Vol.2, No. 1,February1984

Document info
Document views56
Page views56
Page last viewedSun Dec 04 10:29:09 UTC 2016
Pages21
Paragraphs669
Words10995

Comments