Scheduled System Maintenance:
On May 6th, single article purchases and IEEE account management will be unavailable from 8:00 AM - 12:00 PM ET (12:00 - 16:00 UTC). We apologize for the inconvenience.
By Topic

RPC under fire

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)

Although many successful distributed systems have been built using RPC, we have known for a while that it's imperfect, even fundamentally flawed, because it ignores the all-too-real possibility of partial failures by attempting to make the network appear to be just another part of the local environment. A partial failure occurs in a distributed system when a remote application or the network itself fails, thereby introducing the need for applications to handle error conditions that simply cannot arise with local procedure calls. Lately, however, RPC seems to be taking even more heat than usual, mainly because of continuing advances in Web services and XML-based messaging.

Published in:

Internet Computing, IEEE  (Volume:9 ,  Issue: 5 )