Executor

The Executor acts as a container for gCube Tasks, i.e. functionally unconstrained bodies of code that lack a network interface but are designed and packaged to be executed by the service and to be dynamically deployed as the payload of its plugins. In essence, the service publishes descriptive information about dynamically acquired 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.

Functionality

The functionality of the service comprises the static and the dynamic management of tasks:

(in progress)

Design

The design of the service is distributed across two port-types: the Engine and the Task.

(in progress)

The Engine

(in progress)

Tasks

(in progress)

Sample Usage

(in progress)

Sample Task Development

(in progress)