Difference between revisions of "TaskMachine"
(→Key functionality) |
(→Unknowns) |
||
| Line 15: | Line 15: | ||
* What is task memory (is it the task details objects and its persistent storage?) | * What is task memory (is it the task details objects and its persistent storage?) | ||
* How should the completion list be stored? | * How should the completion list be stored? | ||
| + | * Does reverting go back to last checkpoint, or all the way back (or both) | ||
== Diagram == | == Diagram == | ||
[[File:Task_machine.png]] | [[File:Task_machine.png]] | ||
Revision as of 22:40, 29 July 2013
Concept
Allow for arbitrary tasks to run on a machine and give tasks the ability to push new tasks onto the machine for running as well as support tasks having the ability to perform if operations (by popping 2 items off the stack and pushing only one back on). This will allow for a very dynamic capability and simulates a virtual machine in concept. The additional part that taskflow will require is the ability to save/restore the machine (for resumption elsewhere) and the ability to revert (which will require a completion list and checkpoints in said list) to know exactly what tasks the machine has ran and the ability to walk backwards through said tasks to the last checkpoint (or through the whole list).
Key functionality
- Allows for arbitrary complex tasks
- Easily supports subtasks
- Easily supports conditional 'tasks' or operators.
Unknowns
- What is task memory (is it the task details objects and its persistent storage?)
- How should the completion list be stored?
- Does reverting go back to last checkpoint, or all the way back (or both)
Diagram
