Method and system for implementing remote procedure calls in a distributed computer system

• US 5,307,490 A
• Filed: 08/28/1992
• Issued: 04/26/1994
• Est. Priority Date: 08/28/1992
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Tandem Computers Incorporated (HP Inc.)
• Inventors: Kelley, Michael T., Davidson, Thomas J.
• Primary Examiner(s): Heckler, Thomas M.
• Application Number:
  US07/938,102
• Time in Patent Office: 606 Days
• Field of Search: 364/DIG. 1 MS File, 364/DIG. 2 MS File, 395/650, 395/600, 395/725
• US Class Current: 719/328
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 69/00 Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass networks security protocols H04L9/40; wireless communication networks H04W
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and a method for implementing remote procedure calls in a distributed computer system provide a base object class from which all distributed objects can be derived. A program extracting all classes derived from the base class provides an inheritance tree to allow down casting from a root class to a base class and to allow passing high level data structure between participants of a remote procedure call. An Unix script provides stub routines for implementing a client-server model communicating processes.

Claims

1. A structure for sharing data objects in application programs of a distributed computer system, said distributed computer system comprising first and second computers, said structure comprising:

a first application level interface, in said first computer, to a first remote procedure call mechanism;

a second application level interface, in said second computer, to a second remote procedure call mechanism;

means, in said first and second computers, for coupling said first and said second remote procedure call mechanisms, for transporting data between said first and second computers;

first means, coupled to said first application level interface, for providing a data structure representing a base class of sharable objects, each sharable object being accessible by processes in said first and second computers;

second means, coupled to said second application level interface, for providing said data structure representing said base class of sharable objects;

first means, coupled to said first application level interface, for providing data structures representing a plurality of classes of sharable objects each derived, in accordance with a hierarchy of classes, from said base class, each sharable object in each of said plurality of classes of sharable objects being accessible by processes in said first and second computers;

second means, coupled to said second application level interface, for providing said data structures representing said plurality of classes of sharable objects;

first means, in said first computer, for constructing an inheritance tree rooted in a data structure representing said base class, said inheritance tree having data structures representing relationships among said classes of sharable objects and said base class, in accordance with said hierarchy of classes;

second means, in said second computer, for constructing said inheritance tree in said second computer;

first means, in said first computer, for traversing said inheritance tree to construct a data structure representing a relationship between a first object and a second object in said first computer, said first object being specified in a machine-independent format by a process in said second computer via said first and second remote procedure call mechanisms; and

second means, in said second computer, for traversing said inheritance tree to construct a data structure representing a relationship between a first object and a second object in said second computer, said first object being specified by a process in said first computer, via said first and second remote procedure call mechanisms.

2. A structure as in claim 1, wherein each of said sharable objects comprises a server object in a selected one of said first and second computers, and a client object in the other of said first and second computers, said server and client objects communicating via said first and second application level interfaces.

3. A structure as in claim 2, wherein said server object being provided with a plurality of methods to be executed on said selected computer, and said client object accessing each of said methods via a remote procedure call over said first and second application level interfaces.

4. A structure as in claim 3, further comprising means for computing, based on said inheritance tress and using a pointer to a shared object, a pointer to either (a) a parent object containing said shared object, or (b) an included object of said parent object.

5. A structure as in claim 4, wherein said server object maintains a list of sharable objects, and wherein said client object specifies a method in one of said sharable objects in said list using an index into said list, said server object then taking said index to obtain a pointer to said method using said means for computing a pointer.

6. A structure as in claim 3, wherein said server object returns result of executing any one of said methods to said client object via said first and second application level interfaces, and said client object waits in a sleep mode until said result is received.

7. A structure as in claim 3, wherein said server object returns any error message generated during execution of any one of said methods to said client object via said first and second application level interfaces.

8. A structure as in claim 2, wherein said client object belongs to either (a) the server object'"'"'s class of sharable objects, or (b) a class of sharable objects derived from said server object'"'"'s class of sharable objects.

9. A structure as in claim 8, wherein said server object sends said client object a server manifest listing the server object'"'"'s class and classes from which said sever object'"'"'s class is derived, and wherein said client object sends said server object a client manifest listing the client object'"'"'s class and classes from which said client object'"'"'s class is derived.

10. A structure as in claim 2, wherein said client object creates a server communication object and a message notifying said server object creation of said server communication object, and wherein, in response to said message, said server object creates a client communication object for sending messages to said client object.

11. A method for sharing data objects in application programs of a distributed computer system, said distributed computer system comprising first and second computers, said method comprising the steps of:

providing, in said first computer, a first application level interface to a first remote procedure call mechanism in said first computer;

providing, in said second computer, a second application level interface to a second remote procedure call mechanism in said second computer;

coupling said first and second remote procedure call mechanisms in said first and second computers so as to transport data between said first and second computers;

providing a data structure in each of said first and second computers for representing a base class of sharable objects in said first and second computers and providing data structures in each of said first and second computers for representing a plurality of classes of sharable objects each derived from said base class; and

providing, in each of said first and second computers, an inheritance tree rooted in a data structure representing said base class, said inheritance tree having data structures relating, in accordance with a hierarchy, said plurality of classes and said base class; and

traversing, in each of said first and second computers, said inheritance tree to construct a data structure representing a relationship between a first object and a second object, whenever said first object is specified by a process in one of said first and second computers and provided to the other of said first and second computers via said remote procedure call mechanisms in said first and second computers.

12. A method as in claim 11, further comprising the step of implementing each of said sharable objects as a server object in a selected one of said first and second computers, and a client object in the other of said first and second computers, said server and client objects communicating via said first and second application level interfaces.

13. A method as in claim 12, further comprising the step of providing said client object in either (a) the server object'"'"'s class of sharable objects, or (b) a class of sharable objects derived from said server object'"'"'s class of sharable objects.

14. A method as in claim 13, further comprising the steps of:

providing said server object with a plurality of methods to be executed on said selected computer; and

accessing, from said client object, each of said methods via a remote procedure call over said first and second application level interfaces.

15. A method as in claim 14, further comprising the step of computing, in each of said first and second computers, based on said inheritance tree and using a pointer to a shared object, a pointer to either (a) a parent object containing said shared object, or (b) an included object of said parent object.

16. A method as in claim 15, further comprising the steps

maintaining in said server object a list of sharable objects;

specifying an index into said list, when accessing any method in one of said sharable objects in said list; and

taking said index to obtain a pointer to said method using said step for computing a pointer.

17. A method as in claim 14, further comprising the steps of:

returning from said server object a result of executing any one of said methods to said client object via said first and second application level interfaces, and

waiting in a sleep mode of said client object until said result in received.

18. A method as in claim 14, further comprising the step of returning any error message generated during execution of any one of said methods to said client object via said first and second application level interfaces.

19. A method as in claim 13, further comprising the steps of:

sending said client object a server manifest listing the server object'"'"'s class and classes from which said server object'"'"'s class is derived; and

sending said server object a client manifest listing the client object'"'"'s class and classes from which said client object'"'"'s class is derived.

20. A method as in claim 12, further comprising the steps of:

creating in said client object a server communication object and a message notifying said server object creation of said server communication object; and

creating in said server object, in response to said message, a client communication object for sending messages to said client object.