Browse Prior Art Database

Using Task Start/Stopping Thresholds to Determine Task Completion and Cancel-Ability

IP.com Disclosure Number: IPCOM000014452D
Original Publication Date: 2001-Oct-24
Included in the Prior Art Database: 2003-Jun-19
Document File: 2 page(s) / 46K

Publishing Venue

IBM

Abstract

This invention describes a process and method for the cancellation of tasks in progress when an error or other unhandled condition occurs. This method is based on the notion of tracking task completion percentage, and noting whether a task has reached a state based on a completion percentage threshold where it is not cancellable. Consider a newly created task. When the task has just been created the task is considered to be 0% complete. When the operating system runs the task and the task performs works steps toward completion, each step can be assigned a completion percentage. The task can report to the system a completion percentage after each step is completed. The percentage complete can be queried and used in the case where the task encounters an error. System errors, lack of user input, and other errors can make a task eligible for cancellation. The cancellation can take place by the system, independent of the user, for tasks who have not attained a mandatory complete percentage. In systems with constrained resources like PDA's, cells phones, and other systems with limited resources, cancelling non essential tasks can free up resources that will allow other more important and perhaps more complete tasks to be completed. For example consider a task with the following steps and completion percentages. This task does a database lookup to determine the population in the county where the user lives:

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

  Using Task Start/Stopping Thresholds to Determine Task Completion and Cancel-Ability

   This invention describes a process and method for the cancellation of tasks in progress when an error or other unhandled condition occurs. This method is based on the notion of tracking task completion percentage, and noting whether a task has reached a state based on a completion percentage threshold where it is not cancellable.

   Consider a newly created task. When the task has just been created the task is considered to be 0% complete. When the operating system runs the task and the task performs works steps toward completion, each step can be assigned a completion percentage. The task can report to the system a completion percentage after each step is completed.

   The percentage complete can be queried and used in the case where the task encounters an error. System errors, lack of user input, and other errors can make a task eligible for cancellation. The cancellation can take place by the system, independent of the user, for tasks who have not attained a mandatory complete percentage. In systems with constrained resources like PDA's, cells phones, and other systems with limited resources, cancelling non essential tasks can free up resources that will allow other more important and perhaps more complete tasks to be completed.

   For example consider a task with the following steps and completion percentages. This task does a database lookup to determine the population in the county where the user lives:

Task Step Completion Percentage
1. Prompt the user for home state 10%
2. Calculate the population in the state 60%...