Sun Microsystems, Inc. RPC: Remote Procedure Call, Protocol Specication, version 2. Request for Comments RFC 1057, Jun 1988. 66  Home/Search   Document Not in Database   Summary   Related Articles   Check

....back to the client. While RPCs make life easier for the programmer, they pose a number of challenges to the RPC designer, such as target location and activation, binding, parameter format definition and data representation, failure handling, and security. The best known example for RPC is SunRPC [156], a communications Application Program Interface (API) developed by Sun Microsystems in 1988. 2.4 Middleware In the IT industry, middleware is a general term for any software that serves to glue together or mediate between two separate and often already existing programs. 14 In Sun s ....

Sun Microsystems. RPC: Remote Procedure Call, Protocol Specification, Version 2 (RFC 1057), June 1988.

....(like, for instance, preparing for receiving a message) be quite complex, and vary substantially from protocol to protocol. Other interfaces for network programming are also available, but they provide abstractions of higher level than those considered in this paper. Some of them are Sun RPC [17], Corba [11] or the Ada 1 Distributed Systems Annex (DSA) described in annex E of [12] But when an application tries to use them for plain transport layer communications, some problems arise: ffl Transparency of the transport protocol used. These interfaces completely hide the transport ....

....call is received, the handler procedure is automatically called, with the received data as parameter. Asynchronous reception is useful for event driven programming, and is the usual way of building programs for most multicast (such as Isis [3] and Transis [7] and RPC systems (such as Sun RPC [17]) The specification of Bind, Bind Any and Unbind is available as code fragment 3. Code fragment 3 Specification of subprograms for preparing and releasing reception. type HandlerA is access procedure (To: in AddressCA; Data: access Stream) procedure Bind (AnAddress: in AddressCA; Handler: ....

Sun Microsystems. RPC: Remote Procedure Call, protocol specification, version 2. RFC 1057, June 1988.

....implementation. When the server completes the process of the request, the skeleton passes the results back to the client stub, which then returns the results to the client program, along with any exception information. It is worth noting the similarities between this model and the RPC model [Sun88] The Dynamic Invocation Interface (DII) is a generic facility for invoking any operation with a runtime defined parameter list. A dynamic invocation performs four steps: ffl identify the desired object; ffl retrieve its interface (type) ffl construct the invocation; ffl invoke the request, ....

Sun Microsystems. RPC: Remote Procedure Call, Protocol Specification, Version 2, jun 1988. RFC 1057.

....of simplicity, we will refer to the local OM EM even if the tool runs on some other host. In any case, it will be OM EM the tool is directly attached to. oriented local and network wide communication as well as an integrated name service. BCM supports a standard RPC semantics [ZDL 90, Sun88] but also more complex forms of communication, as they arise e.g. through the event trigger mechanism. In addition, BCM provides a mechanism for data conversion in heterogeneous networks, which is based on the NDR protocol (Network Data Representation) ZDL 90] With this protocol, ....

Sun Microsystems. RPC : Remote Procedure Call, Protocol Specification, Version 2. RFC 1057, Sun Microsystems, June 1988.

....connecting machines distributed over a wide area network, instead of a local area or campus net. However, the system is mainly a collection of several popular network file service, name service and communication protocols. The utility for process process interaction is RPC (Remote Procedure Call) Sun88] in which operations are inherently nested, disallowing parallel operation, though there are RPC options to perform multicast singleresponse handshaking. Parallel programming systems have been built on RPC, but they must cheat it in order to leave called processes running and reconnect to them ....

Sun Microsystems, Inc. RPC: Remote Procedure Call. RFC 1057, Sun Microsystems, Inc., June 1988.

....overall structure of the Cedar RPC facility has become standard for remote procedure call packages. There are several other examples of fully implemented RPC systems. These include Xerox Courier [12] Firefly RPC [38] Apollo RPC [14, 44] which is the basis of DCE RPC 2 [16, 44] and Sun RPC [22, 23, 44]. Sun RPC has become a de facto standard, since it is so widely used. DCE RPC, which is actually more versatile, is also gaining acceptance. These are the primary packages to which we will compare our package. The primary design goal for our package was to improve the transparency and generality ....

....the networking , and a port mapper that records the network end points of the procedure servers. Stubs are generated by the rpcgen program, which requires an XDR 3 [23] interface specification. In Sun RPC, the function performed by Grapevine is handled by a name server that runs on every machine [22]. Each name server maintains information about the procedure servers on its own machine. DCE RPC is also very similar to Cedar RPC. Its distributed data base design differs from Cedar in that it has two parts. DCE RPC makes use of a Cell Directory Service, which holds machine and interface ....

[Article contains additional citation context not shown here]

Sun Microsystems Incorporated. RPC: Remote Procedure Call, Protocol Specification, Version 2. Mountain View, California, January 1985.

....serversupplied method implementation. When the server completes the request, the skeleton passes the results back to the client stub, which then returns the results to the client program, along with any exception information. It is worth noting the similarities between this model and the RPC model [4, 19]. One of the main points of using IDL is that the same interface can be compiled to different languages. Therefore, objects written in different languages may coexist in the same system, interacting and exchanging information among them. To allow such interoperability, each target language must ....

Sun Microsystems. RPC: Remote Procedure Call, Protocol Specification, Version 2, jun 1988. RFC 1057.

No context found.

Sun Microsystems, Inc. RPC: Remote Procedure Call, Protocol Specication, version 2. Request for Comments RFC 1057, Jun 1988. 66

No context found.

Sun Microsystems. RPC: Remote Procedure Call, Protocol Specification, Version 2, 1988.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC