Sun Microsystems, Inc.: Remote Procedure Call Specification, Version 2, RFC 1057, June 1988 Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
A Connector Model Suitable for Automatic Generation of Connectors - Bulej, Bures (2003) (Correct)
....a connection crossing distribution boundary, which is established during application startup or at runtime, contrary to implicit or local connection. Since implementation of such connection types is not trivial, its complexity is often hidden in middleware layer, such as CORBA, RMI, SUN RPC [34]. Most middleware platforms create proxy objects which mediate the communication, the common ones being stub at client side and skeleton on server side. Since different types of middleware are not mutually compatible, neither during development process nor during runtime, the middleware platform ....
Sun Microsystems, Inc.: Remote Procedure Call Specification, Version 2, RFC 1057, June 1988
NFS Version 3 - Design and Implementation - Pawlowski, Juszczak, Staubach.. (1994) (36 citations) (Correct)
....connection re establishment. Thus, NFS servers are stupid and NFS clients are smart. NFS Version 3 offers the possibility of potentially smarter clients. 4.2. Multiple version support The Remote Procedure Call (RPC) protocol provides explicit support for multiple versions of a service [RFC1057]. The client and server implementations of NFS Version 3 provide backward compatibility with NFS Version 2 by supporting both NFS Version 2 and NFS Version 3. By default, an RPC client and server bind using the highest version number they both support. Client or server implementations that cannot ....
Sun Microsystems, Inc., "Remote Procedure Call Specification," RFC-1057, DDN Network Information Center, SRI International, Menlo Park, CA.
Infrastructure Support for Adaptive Mobile Applications - Friday (1996) (4 citations) (Correct)
....a similar principle to that introduced in I TCP (see section 3.2.1) specifically the concept of an indirect protocol, i.e. one that uses an intermediary to split connections to mobile hosts into fixed and mobile connections. M RPC has been designed to provide a standard interface based on SunRPC [Sun,88] although additional support for dynamic binding to servers and disconnected operation has been suggested. Each M RPC binding is split into two parts, utilising UDP for the wired hop and RDP (Reliable Data Protocol) to cope with the higher error rates associated with the wireless hop. Like ....
Sun. "Remote Procedure Call Specification", RFC 1050, Sun Microsystems Inc. June 1988.
Relative Debugging for Parallel Systems - David Abramson (1997) (1 citation) (Correct)
....Architecture In order to operate in a parallel environment, Guard97 must be able to control processes executing on various CPU s possibly distributed across a network. The current implementation does this with a client server architecture using the Sun Microsystems RPC communication mechanism [14]. Figure 3.0 shows Guard97 in operation. The client consists of the command line user interface, a graph compiler, and the dataflow interpreter. Interactive commands are converted into remote procedure calls, which are passed to the servers associated with the process name specified in the command ....
Sun Microsystems, Inc., "Remote Procedure Call Specification", RFC-1094, DDN Network Information Center, SRI International, Menlo Park, CA.
NFS: Network File System Version 3 Protocol Specification - Microsystems (1994) (5 citations) Self-citation (Microsystems) (Correct)
....so it could potentially be used on many underlying transport protocols. The NFS service is based on RPC which provides the abstraction above lower level network and transport protocols. The rest of this document assumes the NFS environment is implemented on top of Sun RPC, which is specified in [RFC1057]. A complete discussion is found in [Corbin] External Data Representation The eXternal Data Representation (XDR) specification provides a standard way of representing a set of data types on a network. This solves the problem of different byte orders, structure alignment, and data type ....
....= 19; PATHCONF3res NFSPROC3 PATHCONF(PATHCONF3args) 20; Network File System Version 3 Protocol Specification 2 16 94 Version 3 17 COMMIT3res NFSPROC3 COMMIT(COMMIT3args) 21; 3; 100003; Out of range (undefined) procedure numbers result in RPC errors. Refer to [RFC1057] for more detail. General comments on attributes and consistency data on failure For those procedures that return either post op attr or wcc data structures on failure, the discriminated union may contain the pre operation attributes of the object or object parent directory. This depends on the ....
Sun Microsystems, Inc., "Remote Procedure Call Specification," RFC-1057, DDN Network Information Center, SRI International, Menlo Park, CA. Remote procedure protocol specification.
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