Method for packing/unpacking C operations to/from RPC compatible format using the RPC protocol to operate remotely with an object-oriented repository

• US 6,105,073 A
• Filed: 05/30/1996
• Issued: 08/15/2000
• Est. Priority Date: 05/30/1996
• Status: Expired due to Term

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Choung, Byung-Mee
• Primary Examiner(s): Oberley, Alvin E.
• Assistant Examiner(s): STECHER, PETER S
• Application Number:
  US08/655,553
• Time in Patent Office: 1,538 Days
• Field of Search: 709/300, 709/303, 709/304
• US Class Current: 719/321
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

The present invention provides a C interface program that remotely operates with an object oriented repository by making the public properties and operations of the types in the repository available to Client programs written in the C language, or accessed via DLLs, or shared objects from other languages. Hence, Client program can execute all the operations on a repository, which is operating on a remotely located Server. The Client program source code can be created on the Server and recompiled on the Client platform without the necessity of making any changes to the code.

Claims

1. In a computer system having a server including a CPU, a memory, at least one disk drive and an object-oriented repository, a client remotely located from said server and connected thereto by means of an RPC link, said client including a CPU, a memory, at least one disk drive, and a program operating with said Server for remotely accessing a model stored in said object-oriented repository, said program executing a method for packing and unpacking C functions to and from, respectively, RPC compatible format using RPC protocol, said program comprising the steps of:

a. for each type in said model, determining if a current one of said types is valid for C binding, and if so;

b. generating function numbers for said current type, including;

1) generating object initializer function numbers for said current type;

2) determining if there are more properties for said current type, and if so;

3) for each property for said current type, determining if a current one of said properties is valid for C binding, and if so;

4) generating accessor function numbers for said current property;

5) determining if said current property is not read-only, and if so;

6) generating mutator function numbers for said current property;

7) if there are no more properties for said current type, determining if there are more operations for said current type, and if so;

8) for each operation for said current type, determining if a current one of said operations is valid for C binding, and if so;

9) resolving operation name for said current operation;

10) generating operation numbers for said current operation;

11) if there are no more operations for said current type, generating special function numbers for said current type; and

,

12) returning to said program at step b hereof;

c. generating C client interface packing functions for said current type;

d. generating C server interface unpacking functions for said current type;

e. determining if there are more of said types in said model, and if so, repeating steps a through e hereof;

f. if there are no more types, then;

g. for each data type in said model, determining if a current one of said data types is valid for C binding, and if so;

h. generating C function numbers for said current data type;

i. generating C client interface packing functions for said current data type;

j. generating C server interface unpacking functions for said current data type;

k. determining if there are more data types in said model, and if so, repeating steps h through m hereof; and

,

l. if there are no more data types in said model, stopping said program.

2. A method as in claim 1 wherein said step of generating C Client interface packing functions for said current type further comprises:

a. generating RPC client interface packing object initializer functions for said current type;

b. determining if there are more properties for said current type, and if so;

c. for each property for said current type, determining if a current one of said properties is valid for C binding, and if so;

d. generating C client interface packing code for accessor functions for said current property,

e. determining if said current property is not read-only, and if so;

f. generating C client interface packing code for mutator functions for said current property;

g. if there are no more properties for said type, determining if there are more operations for said type, and if so;

h. for each operation for said type, determining if a current one of said operations is valid for C binding, and if so;

i. resolving operation name for said current operation;

j. generating a C client interface packing function for said current operation;

k. if there are no more operations for said type, generating an RPC client interface packing function for any special operations; and

,

l. returning to step c of claim 1 hereof.

3. A method as in claim 2 wherein said step of generating C Client interface packing code for accessor functions for said current property further comprises:

a. generating function heading with correct parameters for said current property;

b. packaging up model name, class number, function number and parameters of said current property into a record;

c. generating code to RPC clnt_-- call function to initiate a request to said server;

d. generating code for return if RPC call fails;

e. determining if function is an accessor, and if so;

f. generating code to return a value for said accessor; and

,

g. returning to said program at step d of claim 2.

4. A method as in claim 2 wherein said step of generating C Client interface packing code for mutator functions for said current property further comprises:

a. generating function heading with correct parameters for said current property;

b. packaging up model name, class number, function number and parameters of said current property into a record;

c. generating code to RPC clnt_-- call function to initiate a request to said server;

d. generating code for return if RPC call fails;

e. determining if function is an accessor, and if not;

f. returning to said program at step f of claim 2.

5. A method as in claim 2 wherein said step of generating C Client interface packing function for said current operation further comprises:

a. generating function heading with a return type and a parameter list for said operation;

b. determining if there are more parameters, and if so;

c. for each parameter, storing said parameter into a record according to type;

d. when there are no more parameters, generating code to call RPC function clnt_-- call to initiate a request to said server;

e. determining if said current operation has a return value, and if so;

f. generating code to return with null object if said RPC call fails;

g. if said current operation does not have a return value, generating code to return if said RPC call fails;

h. determining if said current operation returns an object or has parameters that do, and if so;

i. generating code to return a value for said object as requested by said client;

j. returning to said program at step h of claim 2 hereof.

6. A method as in claim 1 wherein said step in said server of generating C server interface unpacking functions for said current type further comprises:

a. generating RPC server interface unpacking object initializer functions for said current type;

b. determining if there are more properties for said current type, and if so;

c. determining if a current property for said current type is valid for C binding, and if so;

d. generating C server interface unpacking code for accessor functions for said current property;

e. determining if said current property is not read-only, and if so;

f. generating C server interface unpacking code for mutator functions for said current property;

g. if there are no more properties for said current types, determining if there are more operations for said current type, and if so;

h. determining if a current operation for said current type is valid for C binding, and if so;

i. resolving operation name for said current operation;

j. generating a C server interface unpacking function for said current operation;

k. if there are no more operations for said current type, generating RPC server interface unpacking functions for special operations; and

l. generating a function such that an appropriate C server interface unpacking function for said current type is called; and

,

m. returning to said program at step e of claim 1 hereof.

7. A method as in claim 6 wherein said step of generating C server interface unpacking code for accessor functions for said current property further comprises:

a. generating function heading with correct parameters for said current property;

b. unpacking model name, class number, function number and parameters of said current property transmitted from said client in response to said clnt_-- call;

c. generating code to call accessor function;

d. determining if function is an accessor, and if so;

e. generating code to return a value for said accessor; and

,

f. returning to said program at step d of claim 6.

8. A method as in claim 6 wherein said step of generating C server interface unpacking code for mutator functions for said current property further comprises:

a. generating function heading with correct parameters for said current property;

b. unpacking model name, class number, function number and parameters of said current property transmitted from said client in response to said clnt_-- call;

c. generating code to call a mutator function;

d. determining if function is an accessor, and if not;

e. returning to said program at step f of claim 6.

9. A method as in claim 6 wherein said step of generating a C server interface unpacking function for said current operation further comprises:

a. generating a function heading for said current operation;

b. declaring a local variable for a return value for said current operation;

c. determining if said current operation has a return value, and if so;

d. generating code to set return value for said current operation;

e. generating a code to call said current operation in C binding;

f. determining if there are more parameters, and if so;

g. unpacking a current one of said parameters and pass to C binding call as a parameter;

h. if there are no more parameters, generating a return of said local variable to said client; and

,

i. returning to step j of claim 9 hereof.

10. A method as in claim 6 wherein said step of generating a function to call an appropriate server unpacking function for type further comprises:

a. generating a function heading for said function;

b. generating a switch statement for said function;

c. for each property of type, determining if a current one of said properties is valid for C binding, and if so;

d. generating case statements for accessor and mutator functions for said current property;

e. if there are no more properties for type, for each operation of type, determining if a current one of said operations is valid for C binding, and if so;

f. generating a case statement for name of said current operation;

g. if there are no more operations for type, generating case statements for special operations; and

,

h. returning to said program at step l of claim 6 hereof.

11. A method as in claim 1 wherein said step of generating function numbers for said current data type further comprises:

a. determining if said current data type is not symbolic, and if not;

i) generating object initializer function numbers for said current data type;

ii) generating conversion function numbers for said current data type;

d. determining if said current data type is symbolic, and if so;

e. generating format and conversion function number;

f. if said current data type is not symbolic, generating class id and model id function numbers for said current data type; and

,

g. returning to said program at step i of claim 1 hereof.

12. A method as in claim 1 wherein said step of generating C client interface packing functions for said current data type further comprises:

a. determining if said current data type is not symbolic, and if not;

i) generating RPC client interface packing object initializer functions;

ii) generating RPC client interface packing conversion functions;

b. if said current data type is not not symbolic, determining if said current data type is symbolic, and if so;

c. generating RPC client interface packing format and conversion functions for said current data type;

d. if said current data type is not symbolic, generating class id and model id functions for said current data type; and

,

e. returning to said program at step i of claim 1 hereof.

13. A method as in claim 1 wherein said step in said server of generating C server interface unpacking functions for data types further comprises:

a. determining if said current data type is not symbolic, and if not;

i) generating RPC server interface unpacking object initializer functions;

ii) generating RPC server interface unpacking conversion functions;

b. if said current data type is not not symbolic, determining if said current data type is symbolic, and if so;

c. generating RPC server interface unpacking format and conversion functions for said current data type;

d. if said current data type is not symbolic, generating RPC server interface unpacking class id and model id functions for said current data type;

e. generating a function that makes a switch statement to call an appropriate C server interface unpacking function for said current data type is called; and

,

f. returning to said program at step l of claim 1 hereof.

14. A method as in claim 13 wherein said step of generating a function that makes a switch statement to call an appropriate C server interface unpacking function for said current data type further comprises:

a. generating a heading for said function;

b. determining if said current data type is not symbolic, and if not;

i) generating CASE statements for object initializer functions;

ii) generating CASE statements for conversion functions;

c. if said current data type is not not symbolic, determining if said current data type is symbolic, and if so;

i) generating CASE statements for format;

ii) generating CASE statements for conversion functions for said current data type;

d. if said current data type is not symbolic, generating CASE statements for class id and model id functions for said current data type; and

,

e. returning to said program at step e of claim 13 hereof.

15. In a computer system having a server including a CPU, a memory, at least one disk drive and an object-oriented repository, a client remotely located from said server and connected thereto by means of an RPC link, said client including a CPU, a memory, at least one disk drive, and a program operating with said Server for remotely accessing a model stored in said object-oriented repository, said program executing a method for packing and unpacking C functions to and from, respectively, RPC compatible format using RPC protocol, said program comprising the steps of:

a. for each type in said model, determining if a current one of said types is valid for C binding, and if so;

b. generating function numbers for said current type by;

1) generating object initializer function numbers for said current type;

2) determining if there are more properties for said current type, and if so;

3) for each property for said current type, determining if a current one of said properties is valid for C binding, and if so;

4) generating accessor function numbers for said current property;

5) determining if said current property is not read-only, and if so;

6) generating mutator function numbers for said current property;

7) if there are no more properties for said current type, determining if there are more operations for said current type, and if so;

8) for each operation for said current type, determining if a current one of said operations is valid for C binding, and if so;

9) resolving operation name for said current operation;

10) generating operation numbers for said current operation;

11) if there are no more operations for said current type, generating special function numbers for said current type;

c. generating C client interface packing functions for said current type;

d. generating C server interface unpacking functions for said current type received from said client;

e. determining if there are more of said types in said model, and if so, repeating steps a through e hereof;

f. if there are no more types, then;

g. for each data type in said model, determining if a current one of said data types is valid for C binding, and if so;

h. generating C function numbers for said current data type;

i. generating C client interface packing functions for said current data type;

j. generating C server interface unpacking functions for data types;

k. determining if there are more data types in said model, and if so, repeating steps h through m hereof; and

,

l. if there are no more data types in said model, stopping said program.

16. A method as in claim 15 herein said step of generating C Client interface packing functions for said current type further comprises:

a. generating RPC client interface packing object initializer functions for said current type;

b. determining if there are more properties for said current type, and if so;

c. for each property for said current type, determining if a current one of said properties is valid for C binding, and if so;

d. generating C client interface packing code for accessor functions for said current property,

e. determining if said current property is not read-only, and if so;

f. generating C client interface packing code for mutator functions for said current property;

g. if there are no more properties for said type, determining if there are more operations for said type, and if so;

h. for each operation for said type, determining if a current one of said operations is valid for C binding, and if so;

i. resolving operation name for said current operation;

j. generating a C client interface packing function for said current operation;

k. if there are no more operations for said type, generating an RPC client interface packing function for any special operations; and

,

l. returning to step c of claim 15 hereof.

17. A method as in claim 16 wherein said step of generating C Client interface packing function for said current operation further comprises:

a. generating function heading with a return type and a parameter list for said operation;

b. determining if there are more parameters, and if so;

c. for each parameter, storing said parameter into a record according to type;

d. when there are no more parameters, generating code to call RPC function clnt_-- call to initiate a request to said server;

e. determining if said current operation has a return value, and if so;

f. generating code to return with null object if said RPC call fails;

g. if said current operation does not have a return value, generating code to return if said RPC call fails;

h. determining if said current operation returns an object or has parameters that do, and if so;

i. generating code to return a value for said object as requested by said client;

j. returning to said program at step h of claim 16 hereof.

18. A method as in claim 15 wherein said step in said server of generating C server interface unpacking functions for said current type further comprises:

a. generating RPC server interface unpacking object initializer functions for said current type;

b. determining if there are more properties for said current type, and if so;

c. determining if a current property for said current type is valid for C binding, and if so;

d. generating C server interface unpacking code for accessor functions for said current property;

e. determining if said current property is not read-only, and if so;

f. generating C server interface unpacking code for mutator functions for said current property;

g. if there are no more properties for said current types, determining if there are more operations for said current type, and if so;

h. determining if a current operation for said current type is valid for C binding, and if so;

i. resolving operation name for said current operation;

j. generating a C server interface unpacking function for said current operation;

k. if there are no more operations for said current type, generating RPC server interface unpacking functions for special operations; and

l. generating a function such that an appropriate C server interface unpacking function for said current type is called; and

,

m. returning to said program at step e of claim 15 hereof.

19. A method as in claim 18 wherein said step of generating C server interface unpacking code for accessor functions for said current property further comprises:

a. generating function heading with correct parameters for said current property;

b. unpacking model name, class number, function number and parameters of said current property transmitted from said client in response to said clnt_-- call;

c. generating code to call accessor function;

d. determining if function is an accessor, and if so;

e. generating code to return a value for said accessor; and

,

f. returning to said program at step d of claim 18.

20. A method as in claim 18 wherein said step of generating C server interface unpacking code for mutator functions for said current property further comprises:

a. generating function heading with correct parameters for said current property;

b. unpacking model name, class number, function number and parameters of said current property transmitted from said client in response to said clnt_-- call;

c. generating code to call a mutator function;

d. determining if function is an accessor, and if not;

e. returning to said program at step f of claim 18.

21. A method as in claim 18 wherein said step of generating a C server interface unpacking function for said current operation further comprises:

a. generating a function heading for said current operation;

b. declaring a local variable for a return value for said current operation;

c. determining if said current operation has a return value, and if so;

d. generating code to set return value for said current operation;

e. generating a code to call said current operation in C binding;

f. determining if there are more parameters, and if so;

g. unpacking a current one of said parameters and pass to C binding call as a parameter;

h. if there are no more parameters, generating a return of said local variable to said client; and

,

i. returning to step j of claim 18 hereof.

22. A method as in claim 18 wherein said step of generating a function to call an appropriate server unpacking function for type further comprises:

a. generating a function heading for said function;

b. generating a switch statement for said function;

c. for each property of type, determining if a current one of said properties is valid for C binding, and if so;

d. generating case statements for accessor and mutator functions for said current property;

e. if there are no more properties for type, for each operation of type, determining if a current one of said operations is valid for C binding, and if so;

f. generating a case statement for name of said current operation;

g. if there are no more operations for type, generating case statements for special operations; and

,

h. returning to said program at step l of claim 18 hereof.

23. A method as in claim 15 wherein said step of generating function numbers for said current data type further comprises:

a. determining if said current data type is not symbolic, and if not;

i) generating object initializer function numbers for said current data type;

ii) generating conversion function numbers for said current data type;

d. determining if said current data type is symbolic, and if so;

e. generating format and conversion function number;

f. if said current data type is not symbolic, generating class id and model id function numbers for said current data type; and

,

g. returning to said program at step i of claim 15 hereof.

24. A method as in claim 15 wherein said step of generating C client interface packing functions for said current data type further comprises:

a. determining if said current data type is not symbolic, and if not;

i) generating RPC client interface packing object initializer functions;

ii) generating RPC client interface packing conversion functions;

b. if said current data type is not not symbolic, determining if said current data type is symbolic, and if so;

c. generating RPC client interface packing format and conversion functions for said current data type;

d. if said current data type is not symbolic, generating class id and model id functions for said current data type; and

,

e. returning to said program at step i of claim 15 hereof.

25. A method as in claim 15 wherein said step in said server of generating C server interface unpacking functions for data types further comprises:

a. determining if said current data type is not symbolic, and if not;

i) generating RPC server interface unpacking object initializer functions;

ii) generating RPC server interface unpacking conversion functions;

b. if said current data type is not not symbolic, determining if said current data type is symbolic, and if so;

c. generating RPC server interface unpacking format and conversion functions for said current data type;

d. if said current data type is not symbolic, generating RPC server interface unpacking class id and model id functions for said current data type;

e. generating a function that makes a switch statement to call an appropriate C server interface unpacking function for said current data type is called; and

,

f. returning to said program at step l of claim 15 hereof.

26. A method as in claim 25 wherein said step of generating a function that makes a switch statement to call an appropriate C server interface unpacking function for said current data type further comprises:

a. generating a heading for said function;

b. determining if said current data type is not symbolic, and if not;

i) generating CASE statements for object initializer functions;

ii) generating CASE statements for conversion functions;

c. if said current data type is not not symbolic, determining if said current data type is symbolic, and if so;

i) generating CASE statements for format;

ii) generating CASE statements for conversion functions for said current data type;

d. if said current data type is not symbolic, generating CASE statements for class id and model id functions for said current data type; and

,

e. returning to said program at step e of claim 25 hereof.

27. In a computer system having a server including a CPU, a memory, at least one disk drive and an object-oriented repository, a client remotely located from said server and connected thereto by means of an RPC link, said client including a CPU, a memory, at least one disk drive, and a program operating with said Server for remotely accessing a model stored in said object-oriented repository, said program executing a method for packing and unpacking C functions to and from, respectively, RPC compatible format using RPC protocol, said program comprising the steps of:

a. for each type in said model, determining if a current one of said types is valid for C binding, and if so;

b. generating function numbers for said current type;

c. generating C client interface packing functions for said current type;

d. generating C server interface unpacking functions for said current type;

e. determining if there are more of said types in said model, and if so, repeating steps a through e hereof;

f. if there are no more types, then;

g. for each data type in said model, determining if a current one of said data types is valid for C binding, and if so;

h. generating C function numbers for said current data type;

i. generating C client interface packing functions for said current data type;

j. generating C server interface unpacking functions for said current data type by;

1) generating RPC server interface unpacking object initializer functions for said current type;

2) determining if there are more properties for said current type, and if so;

3) determining if a current property for said current type is valid for C binding, and if so;

4) generating C server interface unpacking code for accessor functions for said current property;

5) determining if said current property is not read-only, and if so;

6) generating C server interface unpacking code for mutator functions for said current property;

7) if there are no more properties for said current types, determining if there are more operations for said current type, and if so;

8) determining if a current operation for said current type is valid for C binding, and if so;

9) resolving operation name for said current operation;

10) generating a C server interface unpacking function for said current operation;

11) if there are no more operations for said current type, generating RPC server interface unpacking functions for special operations; and

12) generating a function such that an appropriate C server interface unpacking function for said current type is called;

k. determining if there are more data types in said model, and if so, repeating steps h through m hereof; and

,

l. if there are no more data types in said model, stopping said program.

28. In a computer system having a server including a CPU, a memory, at least one disk drive and an object-oriented repository, a client remotely located from said server and connected thereto by means of an RPC link, said client including a CPU, a memory, at least one disk drive, and a program operating with said Server for remotely accessing a model stored in said object-oriented repository, said program executing a method for packing and unpacking C functions to and from, respectively, RPC compatible format using RPC protocol, said program comprising the steps of:

a. for each type in said model, determining if a current one of said types is valid for C binding, and if so;

b. generating function numbers for said current type;

c. generating C client interface packing functions for said current type;

d. generating C server interface unpacking functions for said current type;

e. determining if there are more of said types in said model, and if so, repeating steps a through e hereof;

f. if there are no more types, then;

g. for each data type in said model, determining if a current one of said data types is valid for C binding, and if so;

h. generating C function numbers for said current data type;

i. generating C client interface packing functions for said current data type by;

1) generating RPC client interface packing object initializer functions for said current type;

2) determining if there are more properties for said current type, and if so;

3) for each property for said current type, determining if a current one of said properties is valid for C binding, and if so;

4) generating C client interface packing code for accessor functions for said current property,

5) determining if said current property is not read-only, and if so;

6) generating C client interface packing code for mutator functions for said current property;

7) if there are no more properties for said type, determining if there are more operations for said type, and if so;

8) for each operation for said type, determining if a current one of said operations is valid for C binding, and if so;

9) resolving operation name for said current operation;

10) generating a C client interface packing function for said current operation;

11) if there are no more operations for said type, generating an RPC client interface packing function for any special operations;

j. generating C server interface unpacking functions for said current data type;

k. determining if there are more data types in said model, and if so, repeating steps h through m hereof; and

,

l. if there are no more data types in said model, stopping said program.

29. A method as in claim 28 wherein said step of generating C Client interface packing code for accessor functions for said current property further comprises:

a. generating function heading with correct parameters for said current property;

b. packaging up model name, class number, function number and parameters of said current property into a record;

c. generating code to RPC clnt_-- call function to initiate a request to said server;

d. generating code for return if RPC call fails;

e. determining if function is an accessor, and if so;

e. generating code to return a value for said accessor; and

,

f. returning to said program at step d of claim 28.

30. A method as in claim 28 wherein said step of generating C Client interface packing code for mutator functions for said current property further comprises:

a. generating function heading with correct parameters for said current property;

b. packaging up model name, class number, function number and parameters of said current property into a record;

c. generating code to RPC clnt_-- call function to initiate a request to said server;

d. generating code for return if RPC call fails;

e. determining if function is an accessor, and if not;

f. returning to said program at step f of claim 28.

31. A method as in claim 28 wherein said step of generating C Client interface packing function for said current operation further comprises:

a. generating function heading with a return type and a parameter list for said operation;

b. determining if there are more parameters, and if so;

c. for each parameter, storing said parameter into a record according to type;

d. when there are no more parameters, generating code to call RPC function clnt_-- call to initiate a request to said server;

e. determining if said current operation has a return value, and if so;

f. generating code to return with null object if said RPC call fails;

g. if said current operation does not have a return value, generating code to return if said RPC call fails;

h. determining if said current operation returns an object or has parameters that do, and if so;

i. generating code to return a value for said object as requested by said client;

j. returning to said program at step h of claim 28 hereof.