RPC based computer system using transparent callback and associated method

• US 5,247,676 A
• Filed: 02/04/1992
• Issued: 09/21/1993
• Est. Priority Date: 06/29/1989
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Digital Equipment Corporation (HP Inc.)
• Inventors: Lenzmeier, Charles T., Ozur, Mark C., Miller, Thomas J.
• Primary Examiner(s): Fleming, Michael R.
• Assistant Examiner(s): Sheikh, Ayaz R.
• Application Number:
  US07/830,730
• Time in Patent Office: 595 Days
• Field of Search: 395/650, 395/600, 395/200, 364/DIG. 1, 364/DIG. 2
• US Class Current: 719/328
• CPC Class Codes: G06F 9/543 User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]

Abstract

A method is provided for use in a computer system, the method for performing callbacks to a first calling thread that has made an RPC to a second called thread comprising the steps of: creating at least one respective helper thread in the address space of the second called thread; and for each respective created helper thread, providing a respective thread-specific identifying mechanism for identifying the first calling thread.

Claims

1. In a computer system including a calling thread in a client address space, a called server thread in a server address space, means for creating a thread of execution in any specified address space and means for transporting messages between the calling thread and the called server thread;

a method performed by said computer system for processing a remote procedure call by the calling thread to the called server thread, comprising the steps of;

transporting the remote procedure call from the calling thread to the called server thread, identifying the calling thread with a call block and storing said call block in the server address space;

creating in the server address space at least one respective helper thread;

initiating a callback by the at least one respective helper thread to the calling thread; and

performing said initiated callback to the calling thread by accessing said call block to identify the calling thread, and then transporting said callback to the calling thread.

2. The method of claim 1, said computer system further performing the steps of:

upon transporting said callback to the calling thread, storing a callback indicator in said call block to indicate that a callback to the calling thread is in progress;

when said computer system initiates subsequent callbacks from the at least one respective helper thread to the calling thread, accessing said call block to determine whether another callback to the calling thread is in progress, and delaying transportation of each subsequent callback to the calling thread while said callback indicator indicates that another callback is in progress; and

upon completion of each callback, deleting said callback indicator in said call block.

3. The method of claim 2, further including:

blocking transportation of callbacks to the calling thread from the at least one respective helper thread after the called server thread has completed processing of the remote procedure call from the calling thread.

4. The method of claim 2, further including:

upon completing processing of the remote procedure call to the called server thread, storing in the call block a completion indicator indicating that the called server thread has completed processing of the remote procedure call;

during said step of accessing said call block during callbacks by each respective helper thread, determining if said call block contains said completion indicator; and

preventing callbacks by the at least one respective helper thread to the calling thread when said call block contains said completion indicator.

5. The method of claim 1, further including:

upon completing processing of the remote procedure call to the called server thread, storing in the call block a completion indicator indicating that the called server thread has completed processing of the remote procedure call;

during said step of accessing said call block during callbacks by each respective helper thread, determining if said call block contains said completion indicator; and

preventing callbacks by the at least one respective helper thread to the calling thread when said call block contains said completion indicator.

6. The method of claim 1, further including:

blocking transportation of callbacks to the calling thread from the at least one respective helper thread after the called server thread has completed processing of the remote procedure call from the calling thread.

7. The method of claim 1, further including:

storing for each respective helper thread a thread execution block having a pointer to said call block; and

said step of accessing said call block including accessing said respective thread execution block to retrieve said pointer to said call block and then accessing said call block with said retrieved pointer.

8. A computer system comprising:

a calling client thread in a client address space;

a called server thread in a server address space;

remote procedure call (RPC) means for transporting a remote procedure call from the calling thread to the called server thread;

means for identifying said calling thread with a call block and storing said call block in the server address space;

means for creating at least one respective helper thread in the server address space; and

callback means for processing a callback by each respective helper thread to said calling thread by accessing said call block to identify said calling thread and then transporting said callback to said calling thread.

9. The computer system of claim 8, further including:

said callback means including

means for storing in said call block a callback indicator when said computer system initiates a first call back from the at least one respective helper thread to said calling thread to indicate that a callback to said calling thread is in progress;

means for accessing said call block, when said computer system initiates subsequent call backs from the at least one respective helper thread to said calling thread, to determine whether another callback to said calling thread is in progress, and for delaying transportation of each subsequent callback to said calling thread while said callback indicator indicates that another callback is in progress; and

means for deleting said callback indicator in said call block upon completion of each callback.

10. The computer system of claim 8, further including:

means for blocking transportation of callbacks to the calling thread from the at least one respective helper thread after the called server thread has completed processing of the remote procedure call from the calling thread.

11. The computer system of claim 9, further including:

said callback means including;

means for storing in the call block a completion indicator when the called server thread has completed processing of the remote procedure call;

means for determining, while accessing said call bock during callbacks by each respective helper thread, whether said call block contains said completion indicator; and

means for preventing callbacks by the at least one respective helper thread to the calling thread when said call block contains said completion indicator.

12. The computer system of claim 8, further including:

means for blocking transportation of callbacks to the calling thread from the at least one respective helper thread after the called server thread has completed processing of the remote procedure call from the calling thread.

13. The computer system of claim 8, further including:

said callback means including;

means for storing in the call block a completion indicator when the called server thread has completed processing of the remote procedure call;

means for determining, while accessing said call block during callbacks by each respective helper thread, whether said call block contains said completion indicator; and

means for preventing callbacks by the at least one respective helper thread to the calling thread when said call block contains said completion indicator.

14. The computer system of claim 8,

said means for creating including means for storing for each respective helper thread a respective thread execution block having a pointer to said call block;

and

said callback means including means for accessing said call block by accessing said respective thread execution block to retrieve said pointer to said call block and then accessing said call block with said retrieved pointer.