Sun Microsystems. RPC: Remote procedure call protocol specification, 1988.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....version has only a 7 slowdown of a large compilation benchmark over that of a simple IP router. We believe this to be an acceptable overhead for the benefits that Mirage provides. 2 NFS Mirage implements the NFS protocol, version 2. The NFS protocol is based upon SUN Remote Procedure Call (RPC) [Sun88], and therefore uses a request reply paradigm for communication between the clients and the servers. The protocol uses handles to represent files, directories, and other file system objects. An NFS handle is a 32 byte quantity that is generated by the server and opaque to the client. The client ....

Sun Microsystems, "RPC: Remote Procedure Call, Protocol Specification, Version 2", Request for Comments 1057, 1988. 14

....however, technical challenges have impeded the development and deployment of efficient middleware for real time, embedded systems, as described next. 2 Historical Limitations of Middleware for Real time, Following in the tradition of Remote Procedure Call (RPC) 8] toolkits, such as Sun RPC [9] and OSF DCE [10] DOCORBs are well suited for conventional request responsestyle applications running on low speed networks [11] Until recently, however, the QoS specification and enforcement features of conventional DOC middleware and ORBs, as well as their efficiency, predictability, and ....

Sun Microsystems, "RPC: Remote Procedure Call Protocol Specification," Tech. Rep. RFC-1057, Sun Microsystems, Inc., June 1988.

....arguments and the information necessary for a replica site to correctly forge a response back to the client are packaged into a RPC and sent to the Cuckoo service running on the replica site. Necessary information includes the home server s IP address and port number, the SunRPC transaction ID [22] of the operation (available in a reserved field of the Sun RPC structure in some versions of glibc) and the client s IP address and port number. With the operation forwarded, an additional step must be taken: the normal response from the home server to the client must be suppressed. This is to ....

Sun Microsystems, Inc. RPC: remote procedure call protocol specification. Network Working Group, RFC--1050, April 1988.

....memory cannot be allocated; an application has no way to know whether a future malloc operation will fail, so adapting to memory pressure is nearly impossible. The programming models used for Internet services generally fail to express resource constraints in a meaningful way. CORBA [15] RPC [21], Java RMI [22] and now .NET [19] all expose a programming model in which distributed components communicate mainly through remote procedure call, simplifying the harnessing of remote resources through a familiar programming abstraction. Unfortunately this abstraction makes no attempt at exposing ....

Sun Microsystems. RPC: Remote Procedure Call Protocol Specification Version 2. Internet Network Working Group RFC1057, June 1988.

....client process sends a request message to the server process and waits (blocks) for a reply message. Once the reply message is received, caller s execution is resumes and the results of the procedure are extracted from the reply message. Only one of the two processes is active at any given time [Sun1988]. There are numerous RPC packages available, some of which are mentioned in this chapter. At the most fundamental level, these packages are very similar: they are responsible for invoking a particular remote procedure on a server. The fundamentals of RPC calls are discussed in this chapter, ....

Sun Microsystems. RFC 1831: "RPC: Remote Procedure Call Protocol Specification version 2". 1988.

....discuss the two most commonly employed concurrent programming models: thread based concurrency and event driven concurrency. 1. 1 Thread based concurrency The most commonly used design for server applications is the thread or process perrequest model, as embodied in systems such as RPC packages [129], Java Remote Method Invocation [125] and DCOM [95] This model is well supported by modern languages and programming environments, and threading primitives are provided by virtually every commodity operating system. 17 A thread is a context for computation, typically consisting of a program ....

Sun Microsystems Inc. RPC: Remote Procedure Call Protocol Specification Version 2. Internet Network Working Group RFC1057, June 1988.

....can be used to guarantee at most once message delivery; we also discuss our clock requirements and system performance. In Section 3 we discuss how SCMP can be used to provide higher level primitives. In this section we also describe an implementation of at most once RPCs based on the SunRPC library[8], present performance information for our implementation, and compare our performance with zero or more and at most once RPCs already available in the SunRPC library. We conclude with a summary of what we have accomplished. 2. At most once Message Delivery Implementing at most once semantics is ....

....when failures occur such as a crash of the receiving module; it is desirable because it provides proper semantics even when calls are not idempotent. 3.1. An Example: At most once RPC Implementation We have added an SCMP based at most once RPC implementation to the widely used SunRPC library [8], which currently supports UDP and TCP based RPC protocols. Sun s UDP based protocol provides zero or more semantics, which gives only weak guarantees about how many times a call is executed: even when a call terminates normally, it may have been executed more than once. Sun s TCP based protocol ....

Sun Microsystems, Inc. RPC: Remote Procedure Call Protocol specification version 2. Tech. Rept. DARPA-Internet RFC 1057, SUN Microsystems, Inc., June, 1988.

....of the hundreds of sys tem administrators necessary to gather the desired data. Instead, the analysis was done using only data that could be obtained using the Internet 2 with no special privileges or added monitoring facilities. This was principally done by polling hosts using Sun RPC [13] to query rpc.statd to obtain up times and to test availability, and by querying domain servers [7] to obtain host specific information. A surprisingly rich collection of information can be gathered in this fashion, allowing several important parameters to be estimated. Availability is difficult ....

....may describe a host. This made it difficult to precisely identify the manufacturer and model of queried hosts. Often it was impossible to determine more than the manufacturer, or perhaps the processor family. Once the host list was determined, data were gathered by polling each host using Sun RPC [13] to determine the system status, including the length of time it had been up. A time out period of 15 seconds was initially chosen, since a typical round trip time for an ICMP [11] echo request is less than one second, and Sun RPC uses UDP [10] which, like ICMP, is layered on top of IP [12] The ....

Sun Microsystems, Incorporated, "RPC: Remote procedure call protocol specification version 2," Tech. Rep. RFC- 1057, USC Information Sciences Institute, June 1988.

....with the arguments for the remote procedure and does not return from the call until the request has been sent to the server, processed, and a reply received. The message is encoded using XDR so that RPC can be used between heterogeneous machines using different internal data representations [1, 3, 4]. The actual transmission of data is performed using either TCP or UDP depending on the desires of the client and the design of the server. 2.2 Architecture overview of NISC The NISC domain is composed of a directory object and all of its children as shown in Fig. 2. The NISC name space is made ....

Sun Microsystems Inc. 1988. RPC: Remote Procedure Call Protocol Specification.ARPA Network Information Center, April 1988. RFC 1050.

....as IP, TCP, UDP and RTP. While it is possible to achieve a high compression ratio for combinations of these protocols, there are many examples of application specific protocols that could be compressed as well. Examples include AFS [25] HTTP [19] IMAP [11] Java RMI [36] NFS [38] NTP [30] RPC [35], RTSP [51] SDP [24] SNMP [45] various protocols used by networked games (e.g. QNP [47] tunneling protocols (e.g. PPTP [23] protocols used by messaging software (e.g. ICQ [27] AIM [2] and the IMPP work within the IETF [26] and many more. Within a cellular network, it is essential to ....

....[28] Most of these algorithms focus on network and transport layer protocols. However, there are many examples of application specific protocols that could be compressed to save valuable wireless bandwidth. Examples include AFS [25] HTTP [19] IMAP [11] Java RMI [36] NFS [38] NTP [30] RPC [35], RTSP [51] SDP [24] SNMP [45] various protocols used by networked games (e.g. QNP [47] tunneling protocols (e.g. PPTP [23] protocols used by messaging software (e.g. ICQ [27] AIM [2] and the IMPP work within the IETF [26] and many more. Standardization of new algorithms tend to be a ....

Sun Microsystems. Rpc: Remote procedure call protocol specification version 2. Technical report, Jun 1988. RFC-1057.

....Possible examples include: multi threading, persistent state, redundancy, transactional processing, caching and so forth. History of IDL Remote Procedure Calls (RPC) were implemented in the early to mid 1980s. Both Sun and Apollo had early RPC implementations. Sun RPC, defined in RFC 1057 [4], is now referred to as Open Network Computing (ONC) RPC. rpcgen, an IDL compiler like tool, was developed to automate the ONC RPC process. The Apollo RPC research lead to OSF s Distributed Computing Environment (DCE) RPC and its associated IDL and IDL compiler. ONC RPC and DCE IDL are both ....

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

....With two simple textual changes we have converted a program for homogeneous machines to a program which will run on a set of heterogeneous machines. To make this change with systems such as the Open Software Foundation s Distributed Computing Environment (DCE)or Sun s Remote Procedure Call (SunRPC)[8] we would need to: ffl Learn a new language which is used to define the data types for the DCE or SunRPC system ffl Using this language, define the structures in some separate file to be transferred among the programs. Note that every time we change the structures used by the program to share ....

Sun Microsystems. RPC: Remote Procedure Call Protocol specification: Version 2. Sun Microsystems, Inc., June 1988.

.... 9, 1993 1 Kerberos Authentication in Sun RPC Carl Smith The purpose of this report is to describe the Kerberos authentication flavor for Sun RPC and its use for NFS Sun RPC [RFC1057] has an extensible authentication mechanism which allows new authentication flavors to be added from time to time. In SunOS 4.0 DES based authentication was added (with the regrettable misnomer secure RPC ) SunOS 5.0 added support for authentication based on Kerberos version 4 [Steiner] The ....

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

....rather, as load increases, throughput decreases and response time increases dramatically, creating the impression that the service has crashed. 2. 1 Thread based concurrency The most commonly used design for server applications is the threadper request model, as embodied in RPC packages [52], Java Remote Method Invocation [54] and DCOM [37] This model is well supported by modern languages and programming environments. In this 1 Seda is also the Spanish word for silk. dispatcher network dispatch request 1 request 2 request 3 request 4 request N network send result Figure ....

Sun Microsystems. RPC: Remote Procedure Call Protocol Specification Version 2. Internet Network Working Group RFC1057, June 1988.

....data. Interoperability is still an unsolved problem in general, though many approaches have been considered and implemented. Common file formats, from ASCII text to complicated binary records, allow applications to share data via the file system or via UNIX style pipes [6] Remote procedure calls [70] appear as ordinary procedure calls in source code but actually cross address spaces to communicate with other programs. Message passing systems, such as FIELD [61] and its derivatives, broadcast informational messages to any applications that have signed up to listen. Large initiatives today push ....

....software components executing in different address spaces. Heterogeneous RPC is RPC between components written in distinct languages or running on computers with differing data representations. RPC has been implemented in numerous systems. Perhaps the best known RPC implementation is Sun RPC [70], included in virtually every UNIX implementation. A Sun RPC is accomplished by invoking a special call RPC function, so RPCs are easily distinguishable from ordinary procedure calls. A more transparent approach is that of Cedar [12] which adds stub generation for both the caller and the callee ....

[Article contains additional citation context not shown here]

Sun Microsystems. RPC: Remote procedure call protocol specification. Tech. Rep. RFC-1057, Sun Microsystems, Inc., June 1988.

....of abstraction. These systems range from application specific implementations used for basic communications, to well defined standards for message passing programming environments. Message Passing Interface (MPI) DW95] Parallel Virtual Machine (PVM) GBD 94] and Remote Procedure Calls (RPC) [SUN88] are examples of standards in use today. Another is the Horus [RBM96] subsystem comprised of protocol layers which can be combined into a large 14 number of different protocol stacks. Trade offs between efficiency of communication, fault tolerance, load balancing, and security of the system are ....

Sun Microsystems, Inc. (1988, June). RPC: Remote Procedure Call Protocol Specification Version 2. Network Working Group Request For Comments. Mountain View, CA.

.... the originally specified RPC package for 22 NFS [Sun88a] and was based on Diffie Hellman operations over GF(2 n ) which allows fast calculations but is also easier to break [Schneir96] A few months after being released, this security risk motivated a revision of the RPC package to version 2 [Sun88b]. However, AUTH DES was not implemented in early publicly available Unix systems and never achieved wide spread use. Most NFS systems support only the simplest authentication mechanism, AUTH UNIX. In AUTH UNIX, the requestor sends their user ID and group ID along with reach request without any ....

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

....has been modified to interact with a site s Kerberos [Neuman94] infrastructure. Most NFS implementations do not support AUTH KERB, in part, because the security code relies on cryptography that is export controlled. AUTH DES was defined as part of the originally specified RPC package for 22 NFS [Sun88a] and was based on Diffie Hellman operations over GF(2 n ) which allows fast calculations but is also easier to break [Schneir96] A few months after being released, this security risk motivated a revision of the RPC package to version 2 [Sun88b] However, AUTH DES was not implemented in early ....

Sun Microsystems, Inc. RPC: Remote Procedure Call Protocol Specification, Internet RFC 1050, April 1988.

....a time where wireless applications are becoming increasingly important, network protocols and particularly their headers are becoming more varied and more complex. Specialized and application specific protocols (e.g. RTP RTCP [29] RTSP [30] HTTP [9] NFS [25] AFS [14] SDP [12] RDP [26] RPC [34], Java RMI [35] various tunneling protocols, and those of popular media players [28, 3] are proliferating as the networked world moves beyond its previous staples of bulk FTP transfers and telnet. Yet these headers can be bandwidth intensive; for example, the header bandwidth of an RTP ....

SUN MICROSYSTEMS. RPC: Remote Procedure Call Protocol Specification Version 2. Internet Engineering Task Force, Jun 1988. RFC-1057.

....within a Remote Procedure Call (RPC) mechanism. RPC is a wellunderstood programming paradigm which allows the client server interface to look like a programming interface. The exact RPC mechanism that Discuss uses is home brew, because the recent RPC mechanisms, such as Apollo NCS[5] and Sun RPC[19], were not available when Discuss was first built. One nice feature of the Discuss RPC mechanism is that it is designed so that the client and the server can be linked together into a single program. This feature is useful when debugging or writing utilities that need to run quickly. USP The ....

Sun Microsystems, Inc. RPC: Remote Procedure Call Protocol Specification Version 2. Technical Report NIC/RFC 1057, Network Working Group, USC ISI, June 1988.

....the arguments must be copied from an actor user space to MacOS, and back from MacOS to the actor memory space. This leads to general problems in passing arguments and getting results from functions executed in different memory spaces. This kind of problem is encountered in remote procedure calls [11] and the first solution is to copy the arguments and the results from one space to the other. It seems that it is not the best solution for systems acting in close memory space, and before doing anything, we preferred to explore two different fields in this area: a taxonomy of user to system ....

Sun Microsystems, Inc., "RPC: Remote Procedure Call Protocol specification: Version 2", RFC 1057, 1988.

....is done. Remote Procedure Call is a step in this direction. Using this mechanism, the interaction between the two processes appears as a normal procedure call to the programmer. This idea was first proposed by Birrell and Nelson in [5] There are several implementations of this idea such as Sun RPC[24], Apollo RPC[20] etc. Object oriented languages lend themselves rather easily to distributed extensions. All one has to do is to think of objects as independent entities just like processes in the above models. Performing an operation on an object can be visualised as sending a message to the ....

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

....top of an eXternal Data Representation (XDR) The supporting mount protocol allows the server to hand out remote access privileges to a restricted set of clients. It performs the operating system specific functions that allow for example, to attach remote directory trees to some local file system [14]. A key element of the protocol was the desire to have it as stateless as possible. This means that a server need not keep any protocol information about its clients. While this solution provides an extremely robust environment, it does present so problems when attempting to gain meaning ....

....maximum size of the data section of an RPC packet is restricted since for practical reasons, UDP packets cannot be arbitrarily large. Normally, it is assumed that data sets of up to 8 kbytes may be sent over UDP. Implementation details can be found in the appropriate RFC for remote procedure calls [14]. 3 PROPOSED SOLUTION Since the NFS protocol was designed to be stateless, current UNIX operating systems (SOLARIS, HPUX, IRIX) provide very little accounting information relative to remote mounts and amounts of usage. The one exception is the rmtab file . Whenever a remote client mounts a local ....

[Article contains additional citation context not shown here]

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

....performance than signals in the common case. VMMC provides a call that allows a process to block until a notification arrives for it. When a process is waiting for a VMMC message to arrive, this call can be used to switch easily between spinning and blocking as appropriate. 4 SunRPC SunRPC [19] is a widely used remote procedure call interface and specification. SunRPC consists of a set of library functions and a stub generator that follows the XDR [18] standard for data representation. SunRPC is a single thread implementation. The general structure of SunRPC is shown in Figure 1. It is ....

Sun Microsystems, Inc. RPC: Remote Procedure Call Protocol Specification Version 2. Internet Request For Comments RFC 1057, Internet Network Working Group, June 1988.

....lets AFS transfer as much data as it wants in a single call; the amount of data in a single RPC can be over a gigabyte. Rx uses a windowing strategy with packet level acknowledgements. This avoids the send and wait behavior typical of Sun s Open Network Computing Remote Procedure Call (ONC RPC) [5]: because ONC RPC limits the size of any RPC request or response, large files must be transferred in multiple, nonoverlapping calls. Because Rx is based on UDP, it must provide its own mechanisms for flow control, selective retransmit, and authentication. Necessarily, Rx has had to reinvent some ....

Sun Microsystems, Inc., "RPC: Remote Procedure Call Protocol specification: Version 2," RFC 1057, Network Information Center, SRI International (June 1988).

....represent different dimensions in layer interface design. The remainder of this chapter examines each of these in turn. The following chapter considers a prototype interface, selecting one point in the design space. 8 Release Vnode fields Vnode bytes Operation count SunOS 2. 0 (1985) 11 32 24 SunOS 4.0 (1988) 14 40 29 SVR4 no fill (1989) 11 40 37 SVR4 with fill (1989) 19 72 69 Rosenthal s prototype (1990) 6 20 39 Table 2.1: Rosenthal s evaluation of vnode interface evolution in SunOS (from [Ros90] Fill indicates space left in SVR4 for future expansion; Rosenthal s prototype is discussed in ....

....between parallel stacks. the layers. Rather than require that the interface designer keep this information consistent in several different places, operation definitions are combined into an interface definition file. Similar to the data description language used by Sun s rpcgen compiler [Sun87, Sun88] and also Hewlett Packard s NIDL data description language [ZDL 90] this file lists each operation and its arguments 6 . 3.7 Flow of Control Traditional layered services have had a strictly linear behavior. A user would request a service. That user s request would pass down through each ....

Sun Microsystems. "RPC: Remote Procedure Call Protocol specification version 2." Technical Report RFC-1057, Internet Request For Comments, June 1988.

....switch is zero) The second level LR switch will then jump to the label f: in the module to which it is bound. 4.2 Remote procedure call Equanimity uses remote procedure call (RPC) to communicate between client and server. We made this decision due to the availability of a standard RPC package [18] and the similarity of RPC semantics to those in standard programming languages. This choice is purely an implementation decision; we could use message passing just as easily. Parameters to remote modules are marshaled using stub routines built upon the external data representation standard (XDR) ....

Sun Microsystems, Inc. Rpc: Remote procedure call protocol specification version 2. Internet Request for Comments: RFC1057, June 1988.

....of the Proxy Server. 3. HLP RPC Interface: hlp applet rpc insert( hlp applet rpc get xid( hlp applet rpc get direction( hlp applet rpc get prog info( hlp applet rpc put xid( hlp applet rpc put prog info( This interface is specifically designed to provide filtering services for Sun RPC [73] clients and servers residing on the Mobile Host. 4.1.1 HLP MH Application Interface The following calls are used by Mobile Host applications to create and remove pipeline applets within the Proxy Server. 4.1.1.1 Applet Creation The following call is used by an MH application to download an ....

....It would use the hlp applet insert( call to apply a special purpose compression filter to the associated connection. This filter would return compressed data to the client until the connection is terminated, or the filter is recalled via hlp applet remove( 4.1. 3 HLP RPC Interface Sun RPC [73] is an abstraction that is situated between the transport and application layer. Specifically, RPC sits above the transport layer, directly using sockets for communication. Since this mechanism is closely tied to the socket interface, I have implemented an HLP interface specifically for RPC. ....

Sun Microsystems, Inc. RPC: Remote Procedure Call Protocol Specification, Version 2. RFC 1057, IETF Network Working Group, June 1988.

....we present an example to show how this system can be used in supporting fault tolerant, open distributed software development. Section 6 is the remarks. 2 Related Work and the Rationale There have been many successful RPC systems since Nelson s work[18] such as Cedar RPC[5] NCA RPC[22] Sun RPC[16], HRPC[2] and so on. But little of them consider fault tolerance and cross protocol communication in their design, or they relay on users to build up these features. Notable works on incorporating fault tolerance features into RPC systems are the Argus[15] the ISIS[3] 4] and an atomic RPC system ....

Sun Microsystems. RPC: Remote procedure call protocol specification version 2 (RFC 1057). In Internet Network Working Group Request for Comments, No. 1057. Network Information Center, SRI International, June 1988.

....informs the client that all further communication should be directed to the new instance. Since the original server shares no writable memory with the spawned servers, it will be unaffected by any future attempts to invade its privacy (unless it explicitly 2 This protocol is available in Sun RPC [48], which runs under the Unix operating system. 3 DES, or the Data Encryption Standard, is a standard used by the United States government; software using this standard cannot be exported. For a more thorough explanation of encryption standards, see [36] 4 A more complete discussion of secure ....

....RPC g( switch: byte 0 Two name spaces for assembler Figure 5: An LR switch in detail Client Server Data Global Module A Module B Global data resides in a single location. Access is by function call only. Figure 6: Global data accessed by function call decision because a standard RPC package [48] is freely available, and RPC semantics are similar to those in standard programming languages. This choice is purely an implementation decision; we could use message passing just as easily. Parameters to remote modules are marshaled using stub routines built upon the external data representation ....

Sun Microsystems, Inc. RPC: Remote Procedure Call Protocol Specification Version 2. Internet Request for Comments: RFC1057, June 1988.

....challenges have impeded the development and deployment of efficient middleware for real time, embedded systems, as described next. 2 Historical Limitations of Middleware for Real time, Embedded Systems Following in the tradition of Remote Procedure Call (RPC) 8] toolkits, such as Sun RPC [9] and OSF DCE [10] DOC ORBs are well suited for conventional request responsestyle applications running on low speed networks [11] Until recently, however, the QoS specification and enforcement features of conventional DOC middleware and ORBs, as well as their efficiency, predictability, and ....

Sun Microsystems, "RPC: Remote Procedure Call Protocol Specification," Tech. Rep. RFC-1057, Sun Microsystems, Inc., June 1988.

....mechanism between the MiniCache and Venus needs to satisfy two conditions. First, it has to be interruptible in a manner that allows cleanup of state at both ends. Second, it must provide at most once semantics since many of the operations are not idempotent. We initially tried using Sun RPC [6] for communication between the MiniCache and Venus. This would have enhanced the portability of the MiniCache, since Sun RPC is normally available in any kernel that has the Vnode interface. Unfortunately, we found it impossible to meet both the constraints mentioned above using that approach. ....

Sun Microsystems, Inc. RPC: Remote Procedure Call Protocol specification version 2. Tech. Rep. RFC-1057, SRI Network Information Center, June 1988.

....Sockets only consist of instructions for transmission of plain data. It provides data distribution, but it does not allow to start threads on a remote machine. Hence additional mechanisms are required on top of sockets. RMI supports remote method invocation and transfer of objects. Similar to RPC [37, 38], servers contain implementations of procedures. In objectoriented concepts these procedures are called methods. A client calls these methods and waits until they are finished. There already have been objectoriented approaches with RPC in advance of RMI [42] Because RMI allows only unidirectional ....

Sun Microsystems. RPC: Remote Procedure Call Protocol Specification Version 2. Tech. rep., June 1988. RFC1057.

....of the hundreds of system administrators 1 necessary to gather the desired data. Instead, the analysis was done using only data that could be obtained using the Internet 2 with no special privileges or added monitoring facilities. This was principally done by polling hosts using Sun Rpc [16] to query rpc.statd, the icmp echo protocol [14] to test availability, and by polling domain servers [9, 10] to obtain host specific information. A surprisingly rich collection of information can be gathered in this fashion, allowing several important parameters to be estimated. Availability is ....

....This made it difficult to precisely identify the manufacturer and model of queried hosts. Often it was impossible to determine more than the manufacturer, or the processor family. Once lists of hosts were collected for a large number of sites, data were gathered by polling each host using Sun Rpc [16] to determine the system status, including the length of time it had been up. A time out period of 15 seconds was chosen, since a typical round trip time for an icmp echo request is less than 1 second. Sun Rpc uses udp [13] which, like icmp, is layered on top of ip [15] The remaining 14 seconds ....

Sun Microsystems, Incorporated, "RPC: Remote procedure call protocol specification version 2," Tech. Rep. RFC-1057, USC Information Sciences Institute, June 1988.

....semantics at the client similar to normal procedure call. Numerous examples of different RPC services and implementations exist, including Firefly RPC [19] Alphorn [3] lightweight RPC [4] and Peregrine [14] Among the commercial RPC packages released have been Courier from Xerox [24] Sun RPC [22], Netwise RPC from Novell Netware, and NCA from Apollo [2] On the surface, the semantics of RPC seem very simple, yet the reality is that there are subtleties and variations. For example, there are many ways to define how an RPC service deals with server and communication failures. The set of ....

Sun Microsystems. RPC: Remote procedure call protocol specification. Technical Report RFC-1057, Sun Microsystems, Jun 1988.

No context found.

Sun Microsystems, Inc., "RPC: Remote Procedure Call Protocol Specification Version 2", RFC 1057, June 1988. This RFC is being referenced for its description of the AUTH_DH (AUTH_DES) RPC security flavor. http://www.ietf.org/rfc/rfc1057.txt

No context found.

Sun Microsystems, Inc., "RPC: Remote Procedure Call Protocol Specification Version 2", RFC 1057, June 1988. This RFC is being referenced for its description of the AUTH_DH (AUTH_DES) RPC security flavor. http://www.ietf.org/rfc/rfc1057.txt

No context found.

Sun Microsystems, Inc., "RPC: Remote Procedure Call Protocol Specification", RFC 1057, Sun Microsystems, Inc., June 1988. Remote procedure protocol specification.

No context found.

Sun Microsystems, Inc., "RPC: Remote Procedure Call Protocol Specification Version 2", RFC 1057, June 1988. This RFC is being referenced for its description of the AUTH_DH (AUTH_DES) RPC security flavor. http://www.ietf.org/rfc/rfc1057.txt

No context found.

Sun Microsystems. RPC: Remote procedure call protocol specification, 1988.

No context found.

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

No context found.

Sun Microsystems. RPC: Remote procedure call protocol specification. Technical Report RFC-1057, Sun Microsystems, Inc., June 1988.

No context found.

Sun Microsystems. RPC: Remote procedure call protocol specification. Technical Report RFC-1057, June 1988.

No context found.

Sun Microsystems Inc., "RPC: Remote procedure call protocol specification version 2," RFC-1057.

No context found.

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

No context found.

Sun Microsystems Inc., `RPC: Remote Procedure Call protocol specification: Version 2', Technical Report RFC 1057, DARPA, (June 1988). Available as <URL:ftp://ds.internic.net/rfc/rfc1057.txt>.

No context found.

Sun Microsystems Inc, "RPC: Remote Procedure Call Protocol specifications version 2," Request For Comment (RFC) 1057, Internet Publication, June 1988.

No context found.

Sun Microsystems, Inc., RPC: Remote Procedure Call Protocol Specification. Tech. Rept. RFC-1057, DARPA Network Working Group Report, Jun., 1988.

No context found.

Sun Microsystems Inc., RPC: Remote Procedure Call Protocol Specification Version 2, RFC1057, Network Information Center, SRI International, June 1988.

No context found.

Mic88a. Sun Microsystems, Inc, RPC: Remote Procedure Call Protocol Specification, SRI Network Information Center, Menlo Park, CA (June, 1988).

First 50 documents  Next 50

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