By Topic

Convenience Over Correctness

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Vinoski, S. ; Verivue

This article discusses the remote procedure call (RPC) abstraction. RPC has influenced distributed systems research and development since the early 1980s. In that decade, distributed systems such as Argus3 and Emerald4 explored the possibilities for programming languages themselves to be distributed, thereby building distribution directly into any applications written in those languages. Later in the 1980s and into the 1990s, production RPC systems such as the Apollo Network Computing System (NCS), Sun RPC, and the Open Software Foundation (OSF) Distributed Computing Environment (DCE) provided full RPC capabilities for enterprise developers using general-purpose languages such as C and Pascal. That led to the distributed objects era of the 1990s, in which Corba and Microsoft COM developers primarily used C++. RPC also later influenced Java remote method invocation (RMI), Enterprise Java Beans (EJB), XML-RPC, and SOAP.

Published in:

Internet Computing, IEEE  (Volume:12 ,  Issue: 4 )