Transport independent invocation and servant interfaces that permit both typecode interpreted and compiled marshaling

Claim 2

A computer-implemented invocation descriptor data structure for use in a distributed operating computing system that utilizes an object request broker for facilitating communications between different objects associated with the computing system, the computer-implemented invocation descriptor data structure comprising: a compile flag arranged to identify an invocation path type, wherein a first state of the compiled flag indicates that the invocation path type is a static compiled invocation in which marshal and unmarshal functions required to facilitate the invocation are precompiled, and a second state of the compiled flag indicates that the invocation path type is dynamic, typecode interpreted invocation in which the marshal and unmarshal functions required to facilitate the invocation are not precompiled.

Claim 3

A computer-implemented invocation descriptor data structure as recited in claim 1 further comprising: a pointer to an array of parameter descriptor data structures which describe characteristics of parameters associated with the invocation descriptor data structure; and a pointer to an array of pointers to exception descriptor data structures which describe characteristics of exceptions associated with the invocation descriptor data structure.

Claim 4

A computer-implemented invocation descriptor data structure as recited in claim 1 further comprising: a pointer to a reinitialization function which serves to clear buffers associated with the invocation descriptor data structure; and a context descriptor which contains information which is relevant to a method associated with the invocation descriptor data structure.

Claim 5

A computer-implemented invocation descriptor data structure as recited in claim 2 further comprising a descriptor counter which indicates the number of parameters associated with the invocation descriptor data structure.

Claim 6

A computer-implemented invocation descriptor data structure as recited in claim 4 further comprising: a pointer to a reinitialization function which serves to clear buffers associated with the invocation descriptor data structure; and a context descriptor which contains information which is relevant to a method associated with the invocation descriptor data structure.

Claim 7

A computer program product comprising a computer-usable medium having computer-readable code embodied thereon for invoking an object method defined on a distributed server object within a distributed object computing system, the computer program product comprising computer-readable program code for effecting the following steps within the computer system: receiving a request within a client process; selecting a transport appropriate to the request, the transport being used to marshal the request; creating a marshal buffer appropriate to the selected transport, the marshal buffer being used to encapsulate the request; marshaling an argument using descriptor data structures utilizing a marshal method, the descriptor data structures including a compiled flag used to indicate whether the marshal method is typecode interpreted or compiled; and determining whether the compiled flag is set, wherein, when it is determined that the compiled flag is set, the argument marshaling step is accomplished by invoking a marshal method associated with the argument associated with the request; and when it is determined that the compiled flag is not set, the argument marshaling step is accomplished by invoking a typecode marshaling routine passing the argument to the typecode marshaling routine.

Claim 8

A computer program product comprising a computer-usable medium having computer-readable code embodied thereon for invoking an object method defined on a distributed server object within a distributed object computing system, the computer program product comprising computer-readable program code for effecting the following steps within the computer system: receiving a request within a client process; selecting a transport appropriate to the request, the transport being used to marshal the request; creating a marshal buffer appropriate to the selected transport, the marshal buffer being used to encapsulate the request; marshaling an argument using descriptor data structures utilizing a marshal method, the descriptor data structures including a compiled flag used to indicate whether the marshal method is typecode interpreted or compiled; and determining whether the compiled flag is set, wherein, when it is determined that the compiled flag is set, the argument marshaling step is accomplished by invoking a marshal method associated with the argument associated with the request; and when it is determined that the compiled flag is not set, the argument marshaling step is accomplished by invoking a typecode marshaling routine passing the argument to the typecode marshaling routine.

Claim 9

A computer program product for use in a distributed operating environment that utilizes an object request broker for facilitating communications between different objects, the computer program product comprising: computer code for implementing an invocation descriptor data structure, the invocation descriptor data structure including a compile flag arranged to identify an invocation path type, wherein a first state of the compiled flag indicates that the invocation path type is a static compiled invocation in which marshal and unmarshal functions required to facilitate the invocation are precompiled, and a second state of the compiled flag indicates that the invocation path type is a dynamic, typecode interpreted invocation in which the marshal and unmarshal functions required to facilitate the invocation are not precompiled; and a computer readable medium that stores the computer code.

Claim 10

A computer program product for use in a distributed operating environment that utilizes an object request broker for facilitating communications between different objects, the computer program product comprising: computer code for implementing an invocation descriptor data structure, the invocation descriptor data structure including a compile flag arranged to identify an invocation path type, wherein a first state of the compiled flag indicates that the invocation path type is a static compiled invocation in which marshal and unmarshal functions required to facilitate the invocation are precompiled, and a second state of the compiled flag indicates that the invocation path type is a dynamic, typecode interpreted invocation in which the marshal and unmarshal functions required to facilitate the invocation are not precompiled; and a computer readable medium that stores the computer code.

Claim 11

A computer program product as recited in claim 7 further including: computer code for implementing a pointer from within the invocation descriptor data structure to an array of parameter descriptor data structures which describe characteristics of parameters associated with the invocation descriptor data structure; and computer code for implementing a pointer from within the invocation descriptor data structure to an array of pointers to exception descriptor data structures which describe characteristics of exceptions associated with the invocation descriptor data structure.

Claim 12

A computer program product as recited in claim 7 further including: computer code for implementing a pointer form within the invocation descriptor data structure to a reinitialization function which serves to clear buffers associated with the invocation descriptor data structure; and computer code for implementing a pointer from within the invocation descriptor data structure to a context descriptor which contains information which is relevant to a method associated with the invocation descriptor data structure.

Claim 13

A computer program product as recited in claim 8 further including: computer code for implementing a descriptor counter within the invocation descriptor data structure which indicates the number of parameters associated with the invocation descriptor data structure.

Claim 14

A computer program product as recited in claim 9 further including: computer code for implementing a pointer from within the invocation descriptor data structure to a reinitialization function which serves to clear buffers associated with the invocation descriptor data structure; and computer code for implementing a pointer from within the invocation descriptor data structure to a context descriptor which contains information which is relevant to a method associated with the invocation descriptor data structure.