Difference between revisions of "Executor"

Revision as of 23:13, 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

The Engine port-type is the point of contact for clients that wish to launch the execution of tasks. The port-type is stateful, in that it maintains descriptions information about the available tasks. The information is grouped into a single resource bound to the port-type in line with the implied resource pattern of WSRF. In particular, the pairing of the Engine interface and the resource identifies a singleton WS-Resources informally referred to as the engine.

(in progress)

Tasks

(in progress)

Sample Usage

(in progress)

Sample Task Development

(in progress)