Difference between revisions of "Executor"
| Line 7: | Line 7: | ||
The design of the service is distributed across two port-types: the <code>Engine</code> and the <code>Task</code>. | The design of the service is distributed across two port-types: the <code>Engine</code> and the <code>Task</code>. | ||
| − | + | [[Image:ABEDesign1.png]] | |
| + | |||
==== The Engine ==== | ==== The Engine ==== | ||
Revision as of 20:19, 25 August 2009
The Executor acts as a container for gCube tasks, i.e. functionally unconstrained bodies of code that lack a network interface but can be dynamically deployed into the service and executed through its interface. In particular, gCube tasks are designed, packaged, and deployed as plugins of the Executor service.
An instance of the Executor publishes descriptive information about the co-deployed tasks, can execute them on demand on behalf of clients, and can inform clients on the state of their execution. Clients may interact with the Executor service through a library of high-level facilities that subsume standard service stubs to simplify the discovery of service instances and the execution of tasks through those instances.
Design
The design of the service is distributed across two port-types: the Engine and the Task.
The Engine
(in progress)
Tasks
(in progress)
Sample Usage
(in progress)
Sample Task Development
(in progress)
