View in EDS

RPC Under Fire.

Saved in:
Bibliographic Details
Title: RPC Under Fire.
Authors: Vinoski, Steve
Source: IEEE Internet Computing; Sep/Oct2005, Vol. 9 Issue 5, p93-95, 3p
Subject Terms: REMOTE computing, DISTRIBUTED computing, JAVA programming language, APPLICATION program interfaces, XML (Extensible Markup Language)
People: LOUGHRAN, Steve, SMITH, Edmund
Abstract: This article deals with criticisms surrounding the remote procedure call (RPC). 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. Although RPC is sometimes criticized for its synchronous nature, it generally comes under fire for mixing application-level with message-level issues. This commingling has several knock-on detrimental side effects. What seems like a good, simple idea on the surface--hiding networks and messages behind a more familiar application-development idiom--often causes far more harm than good. One particular problem that Steve Loughran and Edmund Smith of Hewlett-Packard Laboratories pointed out at the Java application program interface for Extensible Markup Language-based RPC (JAX-RPC) is the sheer difficulty of mapping between XML and Java. Another fundamental problem that they raised is that its fault-handling approach directly exposes Java faults to other distributed web services.
Database: Complementary Index
Description
Abstract:This article deals with criticisms surrounding the remote procedure call (RPC). 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. Although RPC is sometimes criticized for its synchronous nature, it generally comes under fire for mixing application-level with message-level issues. This commingling has several knock-on detrimental side effects. What seems like a good, simple idea on the surface--hiding networks and messages behind a more familiar application-development idiom--often causes far more harm than good. One particular problem that Steve Loughran and Edmund Smith of Hewlett-Packard Laboratories pointed out at the Java application program interface for Extensible Markup Language-based RPC (JAX-RPC) is the sheer difficulty of mapping between XML and Java. Another fundamental problem that they raised is that its fault-handling approach directly exposes Java faults to other distributed web services.
ISSN:10897801
DOI:10.1109/MIC.2005.108