Method and apparatus for switching long duration tasks from synchronous to asynchronous execution and for reporting task results

• US 6,026,424 A
• Filed: 02/23/1998
• Issued: 02/15/2000
• Est. Priority Date: 02/23/1998
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Circenis, Edgar
• Primary Examiner(s): Banankhah, Majid A.
• Application Number:
  US09/027,691
• Time in Patent Office: 722 Days
• Field of Search: 709/100, 709/102, 709/103, 709/104, 709/107
• US Class Current: 718/104
• CPC Class Codes: G06F 2209/549 Remote execution
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

A client process in a computer system opens a communication channel to a server process in the computer system and instructs the server process to execute a task. The server process starts a timer when it begins execution of the task, to determine whether the task is of short or long duration. If the task completes before the timer reaches a predetermined value, the server process reports task completion to the client process on the open communication channel. If the task does not complete before the timer reaches the predetermined value, the server process closes the communication channel to preserve system resources and continues executing the task asynchronously. When the task is complete, the server process reopens a communication channel and reports task completion to the client process. Results are transmitted directly to the client process only if they are smaller than a predetermined size, otherwise, they are stored in a cache to preserve system resources. The client can then request the results when it is ready to receive them.

Claims

1. In a computer implemented server process, a method of executing tasks in response to a request by a client process, comprising:

a) starting a timer;

b) beginning a task; and

c) if the task does not complete before the timer reaches a predetermined value, initiating freeing of one or more resources which are not essential to completion of the task.

2. A method as in claim 1, wherein the timer is started and the task is begun while a first communication channel between the server process and a client process is open, the first communication channel being one which was initiated by the client process to request execution of the task, the method further comprising:

a) if the task completes before the timer reaches the predetermined value, reporting task completion to the client process via the first communication channel; and

b) if the task does not complete before the timer reaches the predetermined value, initiating opening of a second communication channel and reporting task completion to the client process via the second communication channel.

3. A method as in claim 1, further comprising:

a) storing results of the task in a cache;

b) determining whether the results exceed a predetermined size;

c) if the results do not exceed the predetermined size, transmitting the results to the client process; and

d) if the results exceed the predetermined size, transmitting a notification to the client process that the results are available.

4. A method as in claim 1, wherein at least some of the resources freed are local to the server process.

5. A method as in claim 1, wherein at least some of the resources freed are remote to the server process.

6. In a computer environment comprising a client process and a server process, a method of executing tasks, comprising:

a) the client process initiating opening of a first communication channel to the server process;

b) the client process instructing the server process, via the first communication channel, to execute a task;

c) the server process starting a timer and beginning the task; and

d) if the task does not complete before the timer reaches a predetermined value, initiating freeing of one or more resources which are not essential to completion of the task.

7. A method as in claim 6, further comprising:

a) if the task is completed before the timer reaches a predetermined value, the server process reporting task completion to the client process via the first communication channel;

b) if the task is not completed before the timer reaches the predetermined value, the server process reporting task completion to the client process via a second communication channel established with the client process.

8. A method as in claim 6, further comprising:

a) if the task is not completed before the timer reaches the predetermined value, the server process notifying the client process, via the first communication channel, that the task will be executed asynchronously; and

then

b) initiating closure of the first communication channel.

9. In a computer implemented server process, a method of reporting task results to a client process, comprising:

a) storing task results in a cache;

b) determining whether the task results exceed a predetermined size;

c) if the task results do not exceed the predetermined size, transmitting the task results to a client process; and

d) if the task results exceed the predetermined size, transmitting a notification to a client process that the task results are available.

10. A server process which executes tasks on behalf of one or more client processes, comprising:

a) one or more computer readable storage mediums; and

b) computer readable program code stored in the one or more computer readable storage mediums, the computer readable program code comprising;

i) code for initiating execution of one or more tasks on behalf of one or more client processes;

ii) code for starting one or more timers corresponding to the one or more tasks; and

iii) code for initiating freeing of one or more resources which are not essential to completion of a task if the task does not complete before its corresponding timer reaches a predetermined value.

11. A server process as in claim 10, wherein each of the one or more timers correspond to one of the one or more tasks.

12. A server process as in claim 10, wherein each of the one or more timers correspond to more than one of the one or more tasks.

13. A server process as in claim 10, wherein said predetermined value is set by a user.

14. A server process as in claim 10, wherein said predetermined value is fixed in program code.

15. A server process which executes tasks on behalf of one or more client processes, comprising:

a) one or more computer readable storage mediums; and

b) computer readable program code stored in the one or more computer readable storage mediums, the computer readable program code comprising;

i) code for initiating execution of a task requested via a first communication channel;

ii) code for starting a timer corresponding to the task;

iii) code for initiating freeing of one or more resources which are not essential to completion of the task if the task does not complete before its corresponding timer reaches a predetermined value;

iv) code for reporting task completion via the first communication channel if the task is completed before the timer reaches a predetermined value; and

v) code for initiating opening of a second communication channel and reporting task completion via the second communication channel if the task is not completed before the timer reaches the predetermined value.

16. A server process as in claim 15, further comprising code for:

a) transmitting a notification that the task will be executed asynchronously, via the first communication channel, if the task is not completed before the timer reaches the predetermined value; and

then

b) closing the first communication channel.

17. A server process which reports task results to a client process, comprising:

a) one or more computer readable storage mediums; and

b) computer readable program code stored in the one or more computer readable storage mediums, the computer readable program code comprising;

a) code for storing task results in a cache;

b) code for determining whether the task results exceed a predetermined size;

c) code for transmitting the task results to a client process if the task results do not exceed the predetermined size; and

d) code for transmitting a notification to a client process that the task results are available if the task results exceed the predetermined size.

18. A server process as in claim 17, wherein said predetermined size is set by a user.

19. A server process as in claim 17, wherein said predetermined size is fixed in program code.