Remote procedure call system and method for RPC mechanism independent client and server interfaces interoperable with any of a plurality of remote procedure call backends

[0002] This application is a continuation of U.S. application Ser. No. 08/585,364, filed Jan. 10, 1996, now U.S. Pat. No. 5,887,172.

[0003] 1. Field of Invention

[0004] The present inventions relates to client-server distributed computing systems generally, and more particularly, to systems providing multiple remote procedure call mechanisms dynamically selected at runtime to provide client-server interprocess communication and data transfer.

[0005] 2. Background of Invention

[0006] Client-server computing has become the predominant model of distributed computing, paralleling the increasing performance of desktop computers and workstations. In a client-server distributed computing environment, multiple computers are connected in a network, and a computer may operate both as client, a consumer of resources and data, and a server, a producer of resources and data for the clients. Accompanying the spread of client-server systems, there has been a move away from the homogenous networks common in the past, where there was typically a single or very few vendors providing all the computers, to heterogeneous networks with computers, software, and peripheral devices from multiple vendors. In this environment, integration of client-server operation becomes a critical requirement.

[0007] In any client-server environment, a client requests operations of a server through a remote procedure call (RPC). In a remote procedure call, a process on a local computer, the client, invokes a process, the server, on a remote computer. Historically, the idea was to perform the remote procedure call with a single thread of control held by the client, so that the RPC behaved in the same manner as a local procedure call. In order to achieve this goal, there must be an agreed upon set of semantics between the client and the server for describing the procedure call and specifically, the arguments passed across the call. This is because both the client and the server may have different internal architectures for representing data, and thus, explicit specification of types of arguments is used to communicate data between the client and server. In addition, because the client and server typically are different computers, each with its own address space, passing parameters by reference is not usually possible. Conversion and construction of data for transmission between the client and server is called marshalling. In a general purpose RPC mechanism explicit typing is necessary, since implicit typing cannot be used unless a single RPC mechanism is chosen. In a heterogeneous environment, there may be multiple RPC mechanisms in use, and thus, explicit typing is needed. However, marshalling routines are specific to each RPC mechanism, since they designed to construct the data for a particular and machine architecture RPC mechanism.

[0008] In conventional RPC systems, the client holds an interface to the server in the form of a client stub. The server has a server stub that provides the linkage to the server application. These stubs are created by the application developer by using the interface definition language (IDL) to specify the interface, and then compiled by an IDL compiler. The IDL is used to specify the interface between the client and the server. The client-server interface is conventionally defined as a set of procedures with specifically defined input and output arguments.

[0009] In conventional systems, the semantics of each remote procedure call are implemented when the stubs are compiled by the IDL compiler. The IDL compiler determines the specific marshalling routines for use the arguments in a given procedure, and links these routines into the object code of the interface. The stub is then compiled into the application binary. The resulting, executable binary application code thus, can only be used with the particular RPC mechanism that uses the linked-in marshalling routines. At runtime, there is no ability to select which RPC mechanism to use when several are available, since the marshalling routines are already part of the application.

[0010] In a homogenous computing environment where there is a single RPC mechanism, this approach was acceptable. The selection of a single RPC mechanism ensured that all applications were developed to use just that mechanism. However, homogenous systems are no longer the typical environment. Rather now heterogeneous systems are commonplace where a single RPC mechanism becomes a limitation on the interoperability of clients and servers. Ideally then, a client application should be able to use the services of any server, regardless of the RPC mechanism. That is, where multiple RPC mechanisms are available on the system, the client should be able to select an RPC mechanism when the server is invoked.

[0011] With conventional RPC mechanisms, this is not possible because conventional RPC systems are incompatible and have incompatible APIs. While the individual RPC, mechanisms in and of themselves support heterogeneous environments for different machine architectures, clients and servers do not support heterogeneous operating environments for different RPC mechanisms. More specifically, there are numerous distinct interface definitions languages, each with its own semantics, and with distinct compilers. Each IDL compiler is exclusively tied to distinct RPC mechanism, and each RPC mechanism has its own particular set of marshalling routines for servers using the RPC mechanism. Marshalling routines of one RPC system cannot be used with another. Thus, existing applications that are compiled for use with a specific RPC mechanism cannot be used with other RPC mechanism. This prevent an application selecting an RPC mechanism at runtime.

[0012] To make the application interoperable with other RPC mechanism conventionally requires rewriting the interface of the server in the specific IDL of the new RPC, and then modifying and recompiling the application with the marshalling routine of the RPC. This process is expensive and time consuming, and results in the user having to choose which application to execute depending on which RPC mechanism is desired. The selection of RPC mechanisms is confusing to the user and inefficient.

[0013] Accordingly, it is desirable to use a mechanism that isolates the interface definition of the client-server interface from the RPC mechanism and marshalling routines, so that the RPC mechanism can be dynamically selected when the client is about to use the RPC mechanism on the server. Since the selection is performed at runtime, the client and server can select the RPC mechanism that best suits the operating environment on a per invocation basis. This allows the selection of RPC mechanism to be made at runtime, rather than at compile time, resulting in the desired heterogeneous system flexibility. Deferring selection of marshalling routines to invocation also makes clients and server more portable between hardware platforms and operating systems and allows the addition of new RPC mechanism to an installed base without change to such mechanism.

[0014] In one of its aspects, the present invention overcomes the limitations of conventional RPC systems by creating a canonical specification of a procedure interface at the time that the client or server stub is compiled. When the client stub is subsequently invoked to initiate the remote procedure call, this canonical specification is passed to a selected RPC engine which in turn determines how to marshall the arguments used in the interface and invoke the call. Only when the RPC engine is selected are the marshalling and invocation routines determined. Interpreting the canonical specification at runtime allows for the most optimal implementation of the specification, rather than fixing any form of the implementation at compile time. The resulting implementations from the invention, because they derive directly from the canonical specification, they will offer higher performance than implementations derived from predetermined set of marshalling and invocation routines.

[0015] With the interpreted canonical specification, RPC engine marshalls the interface arguments (if and when necessary) and transmits them to the server by invoking the server stub. The server stub then unmarshalls data, interprets the canonical interface specification to determine the actual arguments and data types, executes the call, and returns the result arguments.

[0016] This process provides a “virtual” remote procedure call (“VRPC”) system. The remote procedure call is “virtual” because the client stub does not have the specific implementation that marshalls the argument at the time of the call. The virtual remote procedure call system separates out the semantics of the procedure call, which are important to the RPC mechanism, from the syntax, which is important to the application developer. In addition, because the determination of RPC engine and the selection of marshalling routines is delayed until runtime, the canonical specification may be optimized where the client and server computers are of the same architecture, by using opaque data types rather than marshalling into machine independent representations. This optimization further improves the performance of the RPC mechanism.

[0017] In one aspect of the invention, the canonical specification is created by an interface definitional language compiler when the stubs are generated. The canonical specification describes the number of arguments, the data type and at least one argument mode in a machine independent manner. In one embodiment, the specification of data type is provided using an agreed set of bytecodes that define the representation format of the canonical specification. Complex data types are specified recursively. The actual data values for the interface arguments are not included in the canonical specification, but determined at runtime. The use of bytecodes enables the VRPC system to be independent of specific RPC mechanisms since the bytecodes define the argument datatypes independently of the machine architecture on which an arbitrary RPC mechanism is implemented. For example, a bytecode specifying an integer datatype may define it to be precisely two bytes in length. In contrast, in conventional programming languages, such as C, the programmer can define a variable to be an integer, but cannot specify that all integers are two bytes. Rather, the computer on which the program is compiled has its own internal format for storing the data and stores the integer in that predetermined format, and that storage format may be different from other integer formats on other computer architectures, even for the exact same program. With the bytecode specification of the present invention, regardless of how the client or server computer internally define an integer, it is stored in the same memory format.

[0018] Another aspect of the present invention is a virtual remote procedure call library and a number of virtual remote procedure call mechanisms, or “VRPC backends.” Each VRPC backend corresponds to a specific RPC system and includes a virtual remote procedure call engine that performs that actual transfer of data across the network, and a set of marshalling routines. The VRPC library facilitates communication between a client stub and a server, and enables the selection of VRPC backend by a client stub.

[0019] Because the selection of RPC mechanisms is deferred until runtime, the use of the VRPC system on a given client machine can be used to select any available RPC mechanism without the need for the VRPC system to be present on other server machines on the network. This provides various advantages, such as allowing any arbitrary RPC mechanism to work with the VRPC system, and thus allowing the client program to use any RPC mechanism without upgrading the server or recompiling the client program. In addition, the VRPC system allows individuals client machines to be upgraded over time, without requiring all clients on a network to use the VRPC system. This reduces the cost and difficulty of migrating a large network to the VRPC system.

[0020] In another aspect of the invention, the use of canonical specifications enables the generation of wire-compatible protocols with existing and unmodified RPC servers of various types. Furthermore, existing interface definition language compilers can be modified to produce VRPC stubs without requiring any change in the underlying programming language. In addition, existing network and RPC-specific libraries may be used to guarantee RPC protocol compatibility.

[0021] FIG. 1 is an illustration of a client-server distributed computing system in accordance with the present invention

[0022] FIG. 2 is a data flow diagram of the process of generating client and server stubs.

[0023] FIG. 3ais an illustration of a type hierarchy for the interface specification.

[0024] FIG. 3bis an illustration of the send call invocation of a VRPC engine.

[0025] FIGS. 4aand 4bare an event trace and data flow diagram of the process of invoking a VRPC engine.

[0026] Referring now to FIG. 1, there is shown one embodiment of the virtual remote procedure call system of the present invention in a client-server distributed computing system. The VRPC system 100 is a distributed client-server system capable of operating with heterogeneous machine architectures. System 100 includes client computers 110 (one client computer 110 is illustrated), coupled to server computers 160 through a network 150. The client computers 110 may be conventional personal computers or workstations, such as Sun Microsystems Inc. SPARCstations, Intel-based x86 computers, IBM 390 or 400 series microcomputers, or the like. In the preferred embodiment, the client and server computers use Sun Microsystems' Solaris 2.x operating system, including the Open Network Computing Plus (ONC+) networking environment.

[0027] The client computers 110 provide both an application development and execution environment for developing application programs in accordance with the present invention. The application development environment 112 includes application programming tools such a code editor, a source code compiler, a linker, a syntax checker, and the like. In accordance with the present invention, an IDL compiler 114 is also provided. The IDL compiler 114 generates client and server stubs that are independent of any rpc mechanism. More particularly, a client stub has no dependencies on interface or network services that defines the marshalling of the input and output arguments of the client stub.

[0028] Rather, the client stub 120 and server stub 164 both include a canonical specification of their interfaces. The canonical specification defines in a machine and RPC-independent manner the data structures and interface routines for the client and server interfaces. The canonical specification uses explicit typing of data structures and interface routines. In the preferred embodiment, the explicit typing is provided by a bytecode specification that is understood by a variety of VRPC backends 140 and marshalling routines 142. The canonical specification is machine readable and can be executed by any VRPC engine 144 to communicate a data stream containing the arguments and data types of the interface between the client and server for a given remote procedure call. A type dictionary 123 created by the IDL compiler 114 and provided in the client 116 and server applications 161 stores the specific types used in the client and server stubs.

[0029] The bytecode specification in the client and server stubs are conventionally compiled with main application source code routines to generate client applications 116 and server applications 161. As compiled, stubs are executable by the application in a normal manner since the stubs have the appropriate syntax for interfacing with their applications.

[0030] In the execution environment, there is provided in the client 110 and server 160 computers a VRPC library 122, and a plurality of VRPC backends 140. The VRPC library 122 provides the communication linkage between the individual client stubs 120 and the server stubs 164 and one of the VRPC backends 140. The VRPC library 122 includes various routines that are invoked by either the client stub or server stub, as necessary to select a VRPC backend 140 and establish a connection therebetween. The routines dynamically select an available VRPC backend 140, passing to it the canonical representation of the interface and the data used by the stub. The selection process is determined at runtime, rather than during compilation of the stubs, as is done conventionally. The VRPC library 122 includes a service provider interface for the VRPC backends 140, so that any VRPC backend 140 can be substituted for any other.

[0031] Each VRPC backend 140 includes a VRPC engine 144 and marshalling routines 146. The VRPC engine 144 receives the canonical specification of the interface provided in the client 120 or server stub 164, along with handles to the data being passed, and calls the appropriate marshalling routines 142 to format the data structures and interface routines according to the bytecode specification in the canonical specification, passing the data values to the marshalling routine 142 since the marshalling routines 142 on the client share the same address space. The bytecode specification only defines the data structures of the interface, it does not specify how these are to be marshalled. Rather, each VRPC engine 144 is responsible for determining which marshalling routines 142 are used. In a preferred embodiment, there are multiple different VRPC backends 140, each specific to a single rpc mechanism, such as ONC-RPC supported by Sun Microsystems, or DCE-RPC, or the like.

[0032] The marshalling routines 142 marshall and unmarshall the passed in arguments, and return them to the VRPC engine 144. These routines are dynamically determined and invoked at runtime, rather than linked into the application binary itself. In this manner, the VRPC engine 144 is selected only when the client is invoked, not when the client stub 120 is generated by the IDL compiler 114 as in conventional systems.

[0033] A naming service 190 provides name to address translation for server applications 161 on the network 150. Each server application 161 on the network 150 has an address, maintained in the naming service 190, and optionally including a specification of which VRPC backend 140 is to be used with the server 161. The server applications 161 are preferably responsible for registering themselves with the naming service 190. The naming service 190 provides the name or address of a server in response to requests from other entities, such as the VRPC library 122 or client application 116.

[0034] Because the selection of VRPC engine 144 and marshalling routines 142 is deferred until runtime, any number of different VRPC engines 144 and marshalling routines 142 can be used with the same client 116 and server stubs 161, without having to recompile the stubs and application for the new rpc mechanism. This allows a single application binary to be distributed and be known to be compatible with current or future rpc mechanisms available on the network, thereby eliminating the cost and difficulty of converting each application to each specific rpc mechanism.

[0035] Generation of Client and Server Stubs

[0036] Referring now to FIG. 2, there is shown a data flow diagram of the process of generating client 120 and server stubs 164. For the purposes of this disclosure, the present invention is described with respect to a development and execution of a single client stub 120 for a single application. Application to the general case will be understood by those of skill in the art.

[0037] The application developer, using the application development environment 112 produces a client application 116 and server application 161 generally as follows. The developer writes a client code 206 and server procedure code 202 in a conventional manner.

[0038] The developer further writes an interface specification for the client and server applications in an IDL language compatible with the IDL compiler. The interface specification defines a set of functions or procedures of the client and server, along with their input and output arguments. In accordance with the invention the, IDL compiler 114 is independent of the RPC mechanism, and so any IDL language compiler is acceptable. Suitable IDL languages includes DCE/RPC IDL, Microsoft's MIDL, CORBA IDL, Sun Microsystems ONC-RPC IDL. In FIG. 2, the interface specification file is illustrated generally by the file foo.x (204).

[0039] The IDL compiler 114 compiles the IDL specification file to produce a client stub 120, here foo_client.c and separately a server stub 164, foo_server.c. The stubs are source code files in a target source language and provide the source code level interfaces for the client and server.

[0040] More particularly, the IDL compiler 114 provides three functions. First, it parses a client-server interface specification described in the input IDL file. The typical IDL language is similar to procedural programming languages, but general provides only structure declarations, function prototypes, and constant expressions. In the preferred embodiment, the IDL compiler 114 may include a number of different front end parsers, each one adapted for handling a different interface definition language.

[0041] Second, the IDL compiler 114 generates programming language specific bindings for the interface specification. This involve mapping parsed interface definitions to the specific programming language and operating system constraints of the execution environment. The language binding of an IDL describes how a particular function or data structure is translated from the IDL language to the target programming language. The output of the IDL compiler 114 is a source file providing a specification of the interface in a form that can be compiled with, and executed by the client and server applications. The preferred target source languages are C and C++.

[0042] Finally, the IDL compiler 114 generates the actual client and server stub code for the language bindings that performs the actual remote procedure calls. Unlike conventional IDL compilers 114 that produce stub code that includes calls to specific marshalling routines for marshalling the data structures of the interface, the stubs produced by the IDL compiler 114 do not specify the marshalling routines to be used for passing the input and output arguments. Rather, the stubs include the canonical specification of the data structures being passed between the client and the server. The canonical representation is maintained in a first data structure, an interface definition structure. The interface definition structure provides an abstract description of the format of the interface, including the data types of the number of input and output arguments, their number, and an identification of the remote procedure. The specification of the data types is provided by a bytecode; each of the VRPC engines 144 is capable of interpreting the bytecodes and determining the proper marshalling routines. A separate data structure or set of data structures is used to point to the argument values themselves.

[0043] The IDL compiler 114 further includes in the client stubs 120 calls to the VRPC library 122 and an abstract VRPC engine 144. These calls pass the interface specification to the VRPC library 122 and VRPC engine 144. Rather, the VRPC library 122 calls a selected VRPC engine 144 in one of the VRPC backends 140, to interpret or compile the implementation of the client interface, and the VRPC engine 144 performs the transformation of the specification into its implementation using its associated marshalling routines. The IDL compiler 114 also includes in a header file for the client stub 120 calls to establish and terminate a connection with the server 161.

[0044] The IDL compiler 114 further produces in the client stub 120 and the server stub 164 a type dictionary 123 that contains all of the data types used in the interface definition. Each data type in the type dictionary 123 is a defined by a series of bytecode sequences. This allows complex data types in the procedure interface to be represented by references to entries in the type dictionary 123. On the server side, the type dictionary 123 is used by the server stub 164 to reconstruct the data types of the raw data received during the remote procedure call.

[0045] FIG. 3aillustrates the type hierarchy of a preferred embodiment of the interface specification 324. The interface specification 324 is illustrated abstractly as an argument to an invocation of a send method of a VRPC engine 144. This invocation is used by the client stub 120 to invoke a selected VRPC engine 144 to make the actual remote procedure call to the server 161. In this embodiment, the interface specification 304 includes a description of the remote procedure interface and a description of the arguments to be supplied to the remote procedure. The description of the remote procedure interface includes:

[0046] an identifier 326 for a procedure number of the particular function procedure. A server interface will typically include a number of procedure calls available from the server. The IDL compiler 114 assigns each of these a unique identifier 326 so that the client and server can reliably exchange information about a specific procedure;

[0047] a variable 328 specifying the type of the return argument value for the remote procedure. This allows the remote procedure to determine the proper marshalling routine for the return value before sending it to the client; and,

[0048] a variable 330 specifying the number of arguments between passed in the procedure call.

[0049] Appendix A includes an exemplary implementation of the type hierarchy of FIG. 3a. In that embodiment, the interface specification 324 is provided in the VRPC_proc_spec_t structure definition.

[0050] In the preferred embodiment the canonical description of the arguments is an argument specification 332 that includes a set of elements that describe each argument. The actual values of the arguments are not included in the argument specification 332, but only their form. For each argument, there is an argument type 336, and at least one argument mode 334. An argument mode 334 specifies the semantics for handling the arguments between the client and server. Generally, the modes define whether an argument is an input or output argument. In the preferred embodiment, the modes are refined to handle different types of relationships and optimization between the client and server. In a “lend” mode, the argument is provided to the server 161, which modifies it and returns the modified value back to the client 120. In a “lend to” mode, the server 161 receives a copy of the argument, and may use that value during the invocation of the remote procedure, and subsequently deallocates memory for that use. The client must still maintain the argument locally. In a “copy to” mode, a copy of the argument is sent to the server 161, which must free its copy upon completion. In a “copy from” mode, the client 116 does not send data to the server 161, but rather receives data having the defined data type. In a “move to” mode, the argument held by the client 116 is deleted after being sent to the server 161, and the server 161 frees this copy after use. Finally, in a “move from” mode, the server 161 passes data to the client 116 and deleted by the server, and the client 116 frees this instance after use.

[0051] An argument type 336 specifies data type for the argument(s). The data type is provided by a bytecode value. The bytecode is used to specify both primitive types, such as ints, chars, and the like, and more complex types that are recursively defined. Appendix A, Section 3.4 includes an exemplary list of bytecodes for representing primitive, pointer, and composed (complex) data types. Other bytecode specifications may also be used. These bytecodes are recognized by the VRPC engines 144, and used by the VRPC engines to select marshalling routines to marshall the arguments into the proper representation for transmission to the server, and then reconstruction by the server.

[0052] In the preferred embodiment, the argument specification structure 332 is included in the procedure interface specification 324, however, in alternate embodiment, the argument specification structure 332 may be separated from the procedure interface specification. FIG. 3aillustrates this relationship. Appendix A provides an exemplary implementation of the argument specification 332, in the VRPC_args_spec_t structure.

[0053] Because the selection of marshalling routines according to the data types of the arguments is delayed until the actual invocation of the server interface, the bytecode specification may be optimized on a per-connection basis to take advantage of the architecture of the client and server computers. More particularly, if both the client and server computers are of the same architecture, such as both Sun Microsystems SPARCstations, then selected data type specific opcodes can be replaced with opaque data types, thereby eliminating the need to marshall the data into a machine independent format. For example, if the data type specified by an opcode is a double, it may be replaced by eight opaque bytes of data. It is significantly more efficient to transmit the eight opaque bytes than to convert a double into an machine independent representation, such as XDR (see below) and then convert back from the machine independent representation to the double. This optimization may be performed by the VRPC engine 144 that is selected at runtime.

[0054] As illustrated in FIG. 3a, the interface specification including the argument specification, are passed to an VRPC engine 144 by invoking its send method. When invoked, the VRPC engine 144 traverses the argument specification 332, and determines from the bytecode specification of the argument types 336 the appropriate marshalling routines. The VRPC engine 144 also separately receives the actual argument values 338. The VRPC engine 144 then calls the marshalling routines to marshall the arguments for transmission to the server 161. This process is further described below with respect to FIG. 4. The client stub 120 further passes to the VRPC engine 144 a state description 380 (FIG. 3) defining the transport parameters for the remote procedure call, and other information, such as the version number 381 of VRPC engine, the name 385 of the VRPC engine, flags 383 for controlling the backend, a handle to the state data 387, and a handle 389 to a destructor function for freeing this state information. An exemplary implementation of the VRPC state description is provided in Appendix A, §4.1.

[0055] A simplified example of a client stub 120 created by an IDL compiler 114 illustrating the canonical form of the interface definition is as follows. Assume that the client stub is to contain a function for summing two variables, A and B. In the IDL file foo.x this function is represented as:

[0056] int sum(int a, int b);

[0057] The IDL compiler 114 creates a canonical specification of this interface in the client stub in the file client.c:

[0058] 1. # include “VRPC.h”

[0059] 2. int sum VRPC_state *be(int a, int b) {

[0060] 3. int tmp;

[0061] 4. void *arg_addr[3];

[0062] 5. arg_addr[0]=&a;

[0063] 6. arg_addr[1]=&b;

[0064] 7. arg_addr[2]=&tmp

[0065] 8. be→send(VRPC_state, inter_descr, arg_addr)

[0066] 9. return(tmp);

[0067] 10.}

[0068] Line 2 defines the interface to the client stub seen by the client application. The interface is consistent with the application's interface as defined in the IDL file. This allows the application to invoke the client stub without the applications developer having to provided any further interfaces between the application and the stub. The body of the stub is hidden from the application, and the application has no information that the sum procedure is being remotely handled. Line 1 specifies the header file which includes the calls for establishing and terminating a connection with a VRPC engine 144. The header file is further described below.

[0069] Line 3 defines the output variable, tmp. This allows the client to have a local handle to a variable for returning the result from the remote procedure to the application. Line 4 defines an array arg_addr that is sized to contain pointers to the two input and one output arguments. In the general case, the argument array contains a pointer for each input and output argument. More generally, in the preferred embodiment, the client stub receives all arguments as pass by reference, including arrays and non-arrays. The argument array corresponds to the argument list 338 in FIG. 3a.

[0070] Lines 5 through 7 define the contents of the arg_addr array, with pointers to the passed in variables a and b, and a pointer to the output variable tmp. In the preferred embodiment, the client stub accepts all arguments as pass by reference, whether these are array or non-array arguments. This arguments array will be passed to one of the VRPC engines and selected marshalling routines. Since these components all reside in the same address space as the client stub, they will be able to access the data values of the argument as need when the data structures of the interface are marshalled at runtime.

[0071] Line 8 performs the remote procedure call itself. This call corresponds to the server interface 302 in FIG. 3a. The canonical specification of the interface is provided as an input argument inter_descr to the send_call function, with inter_descr being an interface specification 324, be is a function pointer to one of the VRPC engines, any of which provide a send_call function. The send_call function passes down the interface specification 324, inter_descr, which here contains a description of the sum function. The send_call further passes the data that accompanies the interface definition, the arg_addr array. When the remote procedure call is completed, the result will be in the temporary variable tmp. As shown in FIG. 3a, the remote procedure call has a return type 340 that indicates whether the remote procedure call was successful or whether there was an error.

[0072] For this example of the function sum( ), the simplified version of the interface specification 324 would be:

[0073] struct {

[0074] int proc_no=1;

[0075] int n_args=3;

[0076] struct arg_spec args [2]={(IN, int_bytecode)

[0077] (IN, int_bytecode),

[0078] (OUT, int_bytecode)};

[0079] }inter_descr;

[0080] where arg_spec is a structure that implements the argument specification described above. The mode values of “IN” and “OUT” are merely illustrative here, and other argument mode values may be used, as described above. Exemplary mode values are described in Appendix A, §3.2, in the VRPC_param_mode_t structure definition. The procedure number, return type, type, and number arguments are determined by the IDL compiler 114.

[0081] As noted above, the interface specification 324 does not contain any of the data being passed between the client and server, but merely the form of that data. Because the data are not included in the canonical representation, this representation can be provided to any VRPC engine 144 for marshalling. Only when the marshalling at runtime is actually performed is the data accessed from the arguments array.

[0082] The client stub described here is a simplified representation of the interface of the client. FIG. 3billustrates an abstract representation of the interface for this invocation. In a preferred embodiment, the invocation 340 of the VRPC library 122 passes in a data structure, here called optab_base_t 353, that encapsulates both the interface specification and argument specification, and an argument list. In addition, the VRPC library 122 receives arguments specifying the version 350 for the client stub 120, flags 352 for setting switches in the library if necessary, the size 354 of the encapsulating structure, for use in marshalling the arguments, a handle 358 to the type dictionary used for the interface, and handles to call the VRPC engine 144 directly for state information (360), its send method 362, and its control method 364. The control method 364 is a general function which the VRPC library 122 uses to instruct the VRPC backend 140 to perform additional functionality. For example, the control method 364 may be used to instruct a VRPC backend 140 to select the security level for a connection between the client and server.

[0083] In addition, a set of function pointers 368 to the client stub 120 are also provided for main routine 118 to call. The VRPC engine 144 also receives the argument list 338 with the actual arguments references for the VRPC engine 144 to marshall. The VRPC engine 144 returns a value 340 indicating whether the remote procedure was successful, or whether an error resulted.

[0084] When the client application 116 first connects with the server, the client invokes the VRPC library 122 to establish a connection and select a VRPC engine 144. The VRPC library 122 initializes the be handle with the address for a selected VRPC engine 144, and client stub function pointers to interface routines. Accordingly, when the client stub 120 is subsequently invoked, it is provided a handle to the VRPC engine 144 which can then marshall the data structures of the interface according to the interface specification structure. The selection process for choosing a VRPC engine 144 at runtime is further described below. The client 116 invokes the VRPC library 122 using interfaces provided in a header file incorporated in all client stubs 120.

[0085] The VRPC library 122 provides two basic functions to the clients: initiation/termination of a connection between client/server and selection of a VRPC engine 144. The interfaces to these functions are provided to a client stub 120 in the VRPC header file 209. More particularly, there is a function to establish a connection to the server using a selected VRPC engine 144. This function takes as an input the name of a server to be conducted, generally provided on the server computer 160, and a handle to the client/server interface being accessed. This function invokes the VRPC library 122 on the client computer 110, which obtains from naming service 190 the name and address of a server 161 including a VRPC engine 144 specified for use by the server application 161 having the server interface. The VRPC library 122 then initializes state variable handle be for contacting the server using that VRPC engine 144. Otherwise, the VRPC library 122 returns a error value. The VRPC library 122 returns the handle to the VRPC backend 140 to the client stub 120. An exemplary interface for this function is VRPC_begin( ) function described in Appendix A, §1.1. Note that the call to VRPC_begin( ) takes an optab_base_t 353 as an argument, thereby providing to the VRPC library 122 the handle to the interface specification and the argument specification in the client sub 116.

[0086] A complementary function terminates a remote procedure call connection through the VRPC engine 144 specified the handle obtained from initiation function. This function is called by the application 166 at the end of its execution. An exemplary interface is shown in Appendix A, §1.1 as VRPC_end( ).

[0087] Exemplary implementations of the VRPC library 122 functions are illustrated in Appendix A, §1.1.

[0088] Execution of Clients and Selection of a VRPC Mechanism

[0089] Referring now to FIGS. 4aand 4bthere is shown an event trace and data low diagram of the process of executing a remote procedure call in accordance with the present invention. The client application 116 containing the remote procedure call is executed on a client computer 110 in a conventional manner. The application 116 includes a call to initialize the handle in the client stub 120 to the VRPC backend 140 used to invoke the backend's send_call method. The application 116 invokes 400 this initialization method, for example VRPC_begin( ), on the VRPC library 122, passing in an identification of a server interface being accessed. The VRPC library 122 is responsible determining the VRPC engine 144 to be used and establishing a connection to the server application 161 using the VRPC engine 144. The VRPC library 122 queries 402 the naming service 190 for the server address and name of the VRPC backend 140. The naming service 190 returns 404 the address of the server 161 and the name of the VRPC backend 140, which the VRPC library 122 then uses to select the VRPC engine 144. Generally, the selection of the VRPC engine 144 is based on the address of the server or the backend name before the connection to the server is established. The address, or the name retrieved from the naming service 190 identifies the specific RPC mechanism to use, and the library 122 knows how to interpret the address from the naming service 190. The client 116 then connects 406 to the server 161 by calling the VRPC library 122, which then establishes the connection to the server 161 with the selected VRPC engine 144 on the client computer 110, and correspondingly with a VRPC engine 144 on the server computer 160. For example, if the address indicates an ONC-RPC mechanism, the library 122 will load in the ONC-RPC backend, and so on. As a consequence of connection being established, the VRPC engine 144 is loaded by the client computer 110. The VRPC library 122 will obtain a handle to the VRPC engine 144 once the VRPC engine 144 is loaded. The VRPC library 122 returns 407 this handle to the client stub 120 so that future invocations of send_call will be made directly on the selected VRPC engine144.

[0090] At some subsequent point, the main routine 118 invokes 409 the client stub 120 by calling one of the procedures defined therein, and passing in some number of arguments. The client stub 120 packages the actual arguments and the argument specification to create the procedure call, specifying the argument mode(s) and type of each argument, and the procedure description, specifying the procedure number, number of arguments, return type. The client stub 120 then invokes 408 the send_call method. This call is forwarded by the VRPC library 122 to the selected VRPC engine 144 on the client computer 110.

[0091] The VRPC engine's 144 on the client computer 110 interprets the interface specification to determine the form of each argument, including its mode(s) and data type according to the bytecode specification. The interpretation further determines from the procedure number the appropriate procedure to invoke on the server 161. From this information, the client's VRPC engine 144 selects the appropriate marshalling routines from the client computer 110 marshalling library 122 for marshalling the arguments into a form that can be transmitted across the network to the server application 161. The VRPC engine 144 invokes 410 these marshalling routines as needed to create the proper representation of an input data structure. Each marshalling routine returns 412 a transport specific data representation for the input data structure. The invocation of the marshalling routines is specific to the VRPC engine 144. In one embodiment based on Sun Microsystems ONC-RPC, the marshalling routines use the data representation specified in XDR: External Data Representation Standard RFC 1104, June 1987. In this environment, the VRPC engine 144 invokes a function clnt_call( ) of the ONC-RPC mechanism that performs the client side of the remote procedure call for any application:

[0092] clnt_call(procedure number,

[0093] *datastruct, *XDRfun,

[0094] *datastruct, *XDRfun))

[0095] This marshalling call specifies the procedure number for the procedure being serviced, and provides pointers to data structures and the marshalling and unmarshalling functions.

[0096] Where the client computer 110 and the server computer 160 are of the same architecture, the client VRPC engine 144 may optimize the bytecodes by using opaque data types, rather than marshalling with the marshalling routines.

[0097] The VRPC engine 144 on the client computer 110 then sends 414 the marshalled data and arguments to the instance of the VRPC engine 144 on the server computer 160. The VRPC engine 144 on the server computer 160 unmarshalls 416 the arguments using the marshalling library 122 on the server computer 160. Referring to FIG. 4B, the marshalling library 122 returns 417 original interface specification to the server's VRPC engine 144.

[0098] The VRPC engine 144 on the server computer 160 interprets 418 the interface specification, using its type dictionary 123, which corresponds to the type dictionary used by the client side VRPC engine 144. This allows the server's VRPC engine 144 to reconstruct the specific data structures of the original arguments, along with identifying the specific procedure to be invoked in the server application. The VRPC engine 144 passes 419 the arguments in the form specified by the interface specification, and procedure number to the server application 161. The server 161 executes 420 the remote procedure on these arguments to obtain the desired result. The server 161 returns 421 the result to the server VRPC engine 144. The server VRPC engine 144 again marshalls 422, 424 the result according to the interface specification, and sends 426 the marshalled data back to the client VRPC engine 144. The client VRPC engine 144 unmarshalls 428, 430 the data with the client marshalling library 122, and forwards 432 the return arguments to the client stub 120, which passes the result to the client application 116.

[0099] 1 VRPC Client Interface . . . 1

[0100] 1.1 Client Initiation . . . 1

[0101] 1.2 Client Stub API . . . 2

[0102] 2 VRPC Server Interface . . . 3

[0103] 2.1 Server Initiation . . . 3

[0104] 3 Interface Specification Mechanism . . . 4

[0105] 3.1 Virtual Data Representation . . . 4

[0106] 3.2 VDR Internals . . . 4

[0107] 3.3 Type Dictionary . . . 6

[0108] 3.4 VDR Bytecode (Type System) . . . 7

[0109] 3.4.1 Canonical Types . . . 7

[0110] 3.4.2 Pointer Types . . . 8

[0111] 3.4.3 Composed and Meta Types . . . 9

[0112] 4 VRPC Backend Interface . . . 10

[0113] 4.1 Interface . . . 10

[0114] 4.2 Backend Support Routines . . . 11

[0115] 4.3 ONC/RPC Opcodes . . . 12

[0116] 4.4 Membuf Opcodes . . . 12

[0117] Functions Index . . . 14

[0118] Data Types Index . . . 15

[0119] Concepts Index . . . 16

[0120] Chapter 1: VRPC Client Interface 1

[0121] These functions are declared in the following header file:

[0122] #include <vrpc/vrpc.h>

[0123] void*vrpc_begin (const char *name, const void Function *clnt_ops)

[0124] Establish VRPC connection.

[0125] name is used to query a naming system to identify and locate the

[0126] server process.

[0127] clnt_ops identifies the interface being accessed. It is the address of a

[0128] appl_optab_t as found in the compiler generated file ‘appl_vclnt.c’.

[0129] vrpc_begin( ) returns a pointer to an initialized appl_optab_t. or nil

[0130] on error.

[0131] int vrpc_end (void*opsp) Function

[0132] Terminate a VRPC connection initiated by vrpc_begin( ).

[0133] opsp is a pointer previously obtained from vrpc_begin( ).

[0134] vrpc_end( ) returns 0 on success and −1 on error.

[0135] int vrpc_begin_buf (const char*name, const void Function *clnt_ops, void*opsp, size_t ops_sz)

[0136] Establish VRPC connection.

[0137] name is used to query a naming system to identify and locate the

[0138] server process.

[0139] clnt_ops identifies the interface being accessed. It is the address of a

[0140] appl_optab_t as found in the compiler generated file ‘appl_vclnt. c’.

[0141] ops is the address of an appl_optab_t to be initialized. Its size is

[0142] passed as the next argument. Its size must match the object pointed

[0143] to by clnt_ops.

[0144] ops_sz is the size of the structure pointed to by opsp.

[0145] vrpc_begin_buf( ) returns 0 on success and −1 on error.

[0146] int vrpc_end_buf (void*opsp) Function

[0147] Terminate a VRPC connection initiated by vrpc_begin_buf( ).

[0148] opsp is the address of a structure previously initialized by vrpc_begin_buf( ). vrpc_end_buf( ) returns 0 on success and −1 on error.

[0149] Chapter 1: VRPC Client Interface 2

[0150] For each remote function defined in the IDL. a client stub routine is generated. Calling this stub function causes the appropriate server function to be invoked with the same arguments: the result of the server routine is returned by the client stub routine.

[0151] int opsp→method (appl_optab_t*opsp, args . . . ) Function

[0152] Make an RPC call. Invokes function method as defined in the IDL.

[0153] opsp is a pointer to an appl_optab_t as initialized by vrpc_begin_buf( ) (see Chapter 1 [Client API]. page 1).

[0154] args are the actual RPC arguments. Note that the VRPC client stub routines all accept arguments as pass-by-reference arguments. All non array arguments are passed by reference. Arrays are also passed by reference. but no additional translation is performed since C already passes arrays by reference.

[0155] Also note that return function values are passed back in the last argument of the argument list. In other words. the function value is converted to a pass-by-reference variable.

[0156] method( ) returns 0 on success and −1 on error.

[0157] Each ‘appl_vclnt.c’ file contains an interface definition. The definition is of type appl_optab_t and is conventionally placed in a variable called APPL_optab.

[0158] appl_optab_t Data type

[0159] typedef struct {

[0160] optab_base_t base;

[0161] int (*func) (appl_optab_t*, const func_arg*, int*func_res);

[0162] . . .

[0163] } appl_optab_t;

[0164] base is of type optab_base_t as described below (see Section 3.2 [VDR Internals]. page 4).

[0165] func each appl_optab_t has one or more members which are function pointers. These are initialized by the compiler generated code to client stubs which perform the corresponding RPC.

[0166] The appl_optab_t has function pointers to the client stubs. Each of these client stubs (ails the be_send_call routine for that appl_optab_t with the appropriate arguments. One of these arguments is a vrpc_proc_spec_t.

[0167] This page under construction.

[0168] Chapter 2: VRPC Server Interface 3

[0169] These functions are declared in the following header file:

[0170] #include <vrpc/vrpc.h>

[0171] void*vrpc_begin (const char*name, const void Function *clnt_ops)

[0172] Establish VRPC connection.

[0173] name is used to query a naming system to identify and locate the server process.

[0174] clnt_ops identifies the interface being accessed. It is the address of a appl_optab_t as found in the compiler generated file ‘appl_vclnt.c’. vrpc_begin( ) returns a pointer to an initialized appl_optab_t. or nil on error.

[0175] This page under construction.

[0176] Chapter 3: Interface Specification Mechanism 4

[0177] VRPC uses a Virtual Data Representation scheme to describe application data structures and procedures. Simply put data structures and procedures defined in an IDL are translated into a specification language which is machine readable. This language consists of specific opcodes (see Section 3.4.1 [bytecode1]. page 7) much like a common assembly language.

[0178] Since the specification is machine readable. these opcodes can be executed by a VRPC backend to properly communicate a data stream between the client and server for a remote procedure call.

[0179] Additionally, specific optimizers can be invoked on a per-connection basis to optimize the byte-code in a way suitable for the architectural characteristics of the client and server machines.

[0180] For example. if the peer machines are of the same architecture (eg. SPARC). then the optimizer can replace most data type specific opcodes in the VDR with opaque data types. For example. a double can be replaced with 8 opaque bytes. It is significantly more efficient to communiate 8 opaque bytes than to convert a double into (for example) XDR and then do the translation from the common format back to a double.

[0181] _version is the version number (1).

[0182] p1 _flags option flags (0).

[0183] _size is the size of the encapsulating appl_optab_t.

[0184] Chapter 3: Interface Specification Mechanism 5

[0185] name is the string name of the interface described by the encapsulating appl_optab_t.

[0186] vdr_tdict is a pointer to the VRPC type dictionary for this interface (see Section 3.3 [typedict]. page 6).

[0187] b_be_handle is a VRPC backend handle.

[0188] p1 b_send_call backend routine that makes RPC call.

[0189] b_ctrl backend control routine.

[0190] opnum the procedure number or unique identifier for this procedure within the scope of this interface.

[0191] rtype_id the type ID of the return value of this function. or 0 if the return type is void.

[0192] nargs the number of arguments this function takes. Also the number of entries in the args array.

[0193] args an array of nargs vrpc_args_spec_ts.

[0194] mode The parameter passing mode.

[0195] type_id The type ID of the argument.

[0196] vrpc_param_mode_t Data type

[0197] enum {

[0198] PM_LEND,

[0199] PM_LEND_TO,

[0200] PM_COPY_TO,

[0201] PM_COPY_FROM,

[0202] PH_MOVE_TO,

[0203] PM_MOVE_FROM

[0204] } vrpc_param_mode_t;

[0205] Chapter 3: Interface Specification Mechanism 6

[0206] PM_LEND The argument is sent to the server, where it is modified, and the modified value is copied back to the client. In a shared memory implementation, this may be implemented as pass-by-reference.

[0207] PM_LEND_TO A copy of the argument is sent to the server. The VRPC runtime frees the server's copy of the arguments when the RPC invocation has completed on the server. The client side instance is not freed.

[0208] PM_COPY_TO A copy of the argument is sent to the server. The server side application code must free its copy. The client side instance is not affected.

[0209] PM_COPY_FROM No data is sent from the client to the server, but data is returned from the server to the client. The server side instance is not freed. The client must free the copy it receives.

[0210] PM_MOVE_TO Client side instance is deleted after call. Server side must free instance. In shared memory implementation. the object is not freed, however, responsibility for freeing object moves from client to server.

[0211] PM_MOVE_FROM Server side instance is deleted after call. Client side must free instance. In shared memory implementation, the object is not freed, however,responsibility for freeing the object moves from the server to client.

[0212] Each ‘appl_vdr.c’ file contains a dictionary of the types represented in that file. The dictionary is of type vrpc_tdict_t and is conventionally (called APPL_typetab.

[0213] The dictionary is simply an array of pinters to opcode sequences. Each of these opcode sequences defines a data type of the interface. When data types are nested, the referene to the nested data type takes the form of an index into the type dictionary

[0214] nctypes Number of type entries in ctype

[0215] ctype Each array entry points to a sequence of vrpc_opcode_ts. Each of these sequences describes a data type used in this VRPC interface specification.

[0216] Chapter 3: Interface Specification Mechanism 7

[0217] Each VRPC backend implements a subset of the following opcodes:

[0218] 3.4.1 Canonical Types

[0219] VRPC_bool32 offset

[0220] a 32 bit boolean.

[0221] VRPC_byte offset

[0222] opaque byte.

[0223] VRPC_int8 offset

[0224] 8 bit char

[0225] VRPC_int16 offset

[0226] 16 bit short

[0227] VRPC_int32 offset

[0228] 32 bit long

[0229] VRPC_int64 offset

[0230] 64 bit long

[0231] VRPC_uint8 offset

[0232] 8 bit unsigned char

[0233] VRPC_uint16 offset

[0234] 16 bit unsigned short

[0235] VRPC_uint32 offset

[0236] 32 bit unsigned long

[0237] VRPC_uint64 offset

[0238] 64 bit unsigned long

[0239] VRPC_enum8 offset

[0240] an 8 bit enum (eg. C++ support)

[0241] VRPC_enum16 offset

[0242] a 16 bit enum

[0243] VRPC_enum32 offset

[0244] a 32 bit enum

[0245] VRPC_enum64 offset

[0246] a 64 bit enum

[0247] VRPC_float32 offset

[0248] a 32 bit float

[0249] VRPC_float64 offset

[0250] a 64 bit float

[0251] Chapter 3: Interface Specification Mechanism 8

[0252] VRPC_float128 offset

[0253] a 128 bit float

[0254] VRPC_char8 offset

[0255] an 8 bit character

[0256] VRPC_char16 offset

[0257] an 16 bit character

[0258] VRPC_char32 offset

[0259] an 32 bit character

[0260] VRPC_zchar8 offset

[0261] an 8 bit zero terminated character

[0262] VRPC_zchar16 offset

[0263] an 16 bit zero terminated character

[0264] VRPC_zchar32 offset

[0265] an 32 bit zero terminated character

[0266] 3.4.2 Pointer Types

[0267] Each of these items describes the type of a pointer. The offset is that of the pointer value.

[0268] VRPC_string8 offset

[0269] a ‘\0’ terminated string of 8 bit chars

[0270] VRPC_string16 offset

[0271] a string of 16 bit chars

[0272] VRPC_string32 offset

[0273] a string of 32 bit chars

[0274] VRPC_string8M max-len offset

[0275] a ‘\0’ terminated string of 8 bit chars

[0276] max-len defines length to malloc for string. excluding ‘\0’ terminator

[0277] VRPC_string16M max-len offset

[0278] a string of 16 bit chars

[0279] VRPC_string32M max-len offset

[0280] a string of 32 bit chars

[0281] VRPC_pointer1 ptr-offset type-instr

[0282] pointer to 1 instance of type-instr

[0283] VRPC_pointerN n-count ptr-offset type-instr

[0284] pointer to n-count instances of type-instr

[0285] Chapter 3: Interface Specification Mechanism 9

[0286] VRPC_pointerL len-instr val-offset type-instr

[0287] pointer to L instances of type-instr

[0288] VRPC_pointerML max-count len-instr val-offset type-instr

[0289] pointer to len-instr( ) instances in buf of size max-count

[0290] VRPC_appl

[0291] a pointer to an upcall routine

[0292] 3.4.3 Composed and Meta Types

[0293] VRPC_nop

[0294] do nothing.

[0295] VRPC_nest type-id offset

[0296] a reference to another type

[0297] VRPC_vector count type-instr

[0298] fixed sized array of length count of type type-instr

[0299] VRPC_array

[0300] an array

[0301] VRPC_struct struct-size struct-name

[0302] a struct

[0303] VRPC_estruct

[0304] end of a struct

[0305] VRPC_SunionC union_size

[0306] union-offset disc-instr ncases default-type-id

[0307] (case. type-id)

[0308] union-in-struct with cases

[0309] VRPC_RTerror

[0310] force runtime error

[0311] Chapter 4: V RPC Backend Interface 10

[0312] A VRPC backend is expected to export the following interface. The backend must be implemented as a shared library that the VRPC library can dlopen( ).

[0313] The shared library must have an entry point (function) which uses its arguments to construct and return a pointer to a vrpc_be_ops_t.

[0314] vrpc_be_ops_t*vrpc_create_ADDR (const Function vrpc_tdict_t*ty, const void*addr-info)

[0315] ADDR is the actual name assigned to the particular VRPC backend.

[0316] TY is the applications type dictionary (see Section 3.3 [typedict]. page 6).

[0317] addr-info is some backend specific address information. This information may be used to connect to the RPC server.

[0318] vrpc_create_ADDR( ) returns the address of an initialized vrpc_be_ops_t or nil on error.

[0319] Note that the destructor for this data type is called using a function pointer within the data type.

[0320] This type is used to hold state information for a VRPC backend.

[0321] be_flags is used to hold state flags.

[0322] be_version is used to indicate the backend version.

[0323] be_name holds the name of the backend.

[0324] be_data is used by the backend to store a pointer to its own private state information.

[0325] be_untransport points to a destructor function for be_data. When it is non nil, it is called by the VRPC runtime with be_data as an argument when the vrpc_be_ops_t is destroyed.

[0326] Chapter 4: RPC Backend Interface 11

[0327] const op*peek_int (const op*ip, const void*dp, Function unsigned long*res)

[0328] This function returns an integer from memory. It is typically used to determine the dimension of dynamically sized arrays and discriminators in unions. The instruction sequence must consist of canonical types.

[0329] ip points to the instruction sequence describing the type of integer to read.

[0330] dp points to the user's data structure (integers.

[0331] res points to where the read integer is returned.

[0332] peek_int( ) returns the value of the advanced ip.

[0333] const op*poke_int (const op*ip, const void*dp, Function const unsigned long*val)

[0334] This function writes an integer to memory. It is typically used to set the dimension of dynamically sized arrays and discriminators in unions. The instruction sequence must consist of canonical types.

[0335] ip points to the instruction sequence describing the type of integer to write.

[0336] dp points to the user's data structure (integer).

[0337] val points to the integer value to be written to memory.

[0338] poke_int( ) returns the value of the advanced ip.

[0339] size_t size_at (const op*const*tdict, const op*ip) Function

[0340] This function returns the size of an object described in VDR.

[0341] tdict points to the type dictionary to be used.

[0342] ip points to the instruction sequence describing the object.

[0343] size_at( ) returns the size of the object in bytes.

[0344] const op*skip1_at (const op*ip) Function

[0345] This function advances the instruction pointer to the next VDR instruction.

[0346] ip points to the instruction sequence to be skipped.

[0347] skip1_at( ) returns the value of the advanced ip.

[0348] const op*has_pointer (const op*const*tdict, Function const op*ip, int*res)

[0349] This function examines the pointed to object and decides whether the described object contains any pointers.

[0350] tdict is the type dictionary.

[0351] Chapter 4: VRPC Backend Interface 1

[0352] ip is the address of the VDR description of the object to be examined.

[0353] res points to an int where this function returns its value. It is set to TRUE if a pointer is found. and FALSE if no pointers are found.

[0354] has_pointer( ) returns the value of the advanced ip.

[0355] The following opcodes are implemented by the ONC/RPC backend module.

[0356] VRPC_RTerror

[0357] VRPC_SunionC

[0358] VRPC_bool32

[0359] VRPC_byte

[0360] VRPC_enum32

[0361] VRPC_estruct

[0362] VRPC_float{32.64.128}

[0363] VRPC_nest

[0364] VRPC_nop

[0365] VRPC_pointerML

[0366] VRPC_pointerN

[0367] VRPC_string8

[0368] VRPC_string8M

[0369] VRPC_struct

[0370] VRPC_vector

[0371] VRPC_{,u}int{8.16.32}

[0372] The following opcodes are implemented by the Membuf backend module. Note that the Solaris/Doors backend is built on top of the membuf backend.

[0373] VRPC_RTerror

[0374] VRPC_SunionC

[0375] VRPC_bool32

[0376] VRPC_byte

[0377] VRPC_enum32

[0378] VRPC_estruct

[0379] VRPC_float{32.64.128}

[0380] Chapter 4: VRPC Backend Interface 13

[0381] VRPC_nest

[0382] VRPC_nop

[0383] VRPC_pointerML

[0384] VRPC_pointerN

[0385] VRPC_string8

[0386] VRPC_string8M

[0387] VRPC_struct

[0388] VRPC_vector

[0389] VRPC_{.u}int{8.16.32}

[0390] Functions Index 14

[0391] H

[0392] has_pointer . . . 11

[0393] O opsp→method . . . 2

[0394] P

[0395] peek_int . . . 11

[0396] poke_int . . . 11

[0397] S

[0398] size_at . . . 11

[0399] skip1_at . . . 11

[0400] V

[0401] vrpc_begin . . . 1.3

[0402] vrpc_begin_buf . . . 1

[0403] vrpc_create_ADDR . . . 10

[0404] vrpc_end . . . 1

[0405] vrpc_end_buf . . . 1

[0406] Data Types Index 15

[0407] A

[0408] appl_optab_t . . . 2

[0409] O

[0410] optab_base_t . . . 4

[0411] V

[0412] vrpc_args_spec_t . . . 5

[0413] vrpc_be_ops_t . . . 10

[0414] vrpc_param_mode_t . . . 5

[0415] vrpc_proc_spec_t . . . 5

[0416] vrpc_tdict_t . . . 6

[0417] Concepts Index 16

[0418] B

[0419] Backend Interface . . . 10

[0420] C

[0421] Client API . . . 1

[0422] Client Stub API . . . 2

[0423] M

[0424] Membuf Opcodes . . . 12

[0425] O

[0426] ONC/RPC Opcodes . . . 12

[0427] Opcodes . . . 7

[0428] S

[0429] Server API . . . 3

[0430] T

[0431] Type Dictionary Layout . . . 6

[0432] V

[0433] VDR Theory . . . 4