File system based task queue management
First Claim
1. An apparatus comprising:
- task producer code, when executed, causing one or more executable files corresponding to each of one or more tasks to be stored in a queue directory responsive to receiving the one or more tasks, wherein a file system is configured to provide each of the executable files with a time stamp indicating when an associated one of the executable files was stored; and
task consumer code, when executed, causing the one or more executable files to execute in an order indicated by the time stamp associated with each of the executable files and to remove each of the executable files after execution, wherein the task producer and task consumer code are tangibly embodied on one or more computer readable storage media.
4 Assignments
0 Petitions
Accused Products
Abstract
A task queue management technique leverages infrastructure provided by file and operating systems to manage task queues substantially without otherwise typical problems regarding management of the size of the queue and/or the state of the queue (e.g., empty or full) while maintaining, regulating and altering the queue and the order of tasks in the queue. Task producer code is configurable to cause one or more executable files corresponding to each of one or more tasks to be stored in a queue directory responsive to receiving the one or more tasks. A file system associates each executable file with a time stamp indicating when the executable file was stored. Task consumer code is configurable to execute the one or more executable files in an order indicated by the time stamps associated with the executable files and to remove each executable file after execution of each executable file.
-
Citations
18 Claims
-
1. An apparatus comprising:
-
task producer code, when executed, causing one or more executable files corresponding to each of one or more tasks to be stored in a queue directory responsive to receiving the one or more tasks, wherein a file system is configured to provide each of the executable files with a time stamp indicating when an associated one of the executable files was stored; and task consumer code, when executed, causing the one or more executable files to execute in an order indicated by the time stamp associated with each of the executable files and to remove each of the executable files after execution, wherein the task producer and task consumer code are tangibly embodied on one or more computer readable storage media. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method of managing a task queue of a computer system, comprising:
-
storing first code for performing a first task in a first file with a first time stamp in a queue directory of the computer system; storing second code for performing a second task in a second file with a second time stamp in the queue directory; and accessing one of the first and second code to perform a next task, the next task being determined dependent upon the first and second time stamps, wherein the first and second time stamps indicate when the first and second files, respectively, were stored. - View Dependent Claims (9, 10, 11, 12, 13, 14, 15, 16, 17)
-
-
18. A method of managing a task queue comprising:
-
generating software program tasks by a first execution environment; causing executable files corresponding to the generated software program tasks to be stored in a queue directory which is accessible by the first execution environment and a second execution environment, wherein a file system associates each of the executable files with a time stamp indicating when each of the executable files were stored; executing the executable files by the second execution environment in an order indicated by the time stamp associated with each of the executable files; and removing each of the executable files after execution.
-
Specification