Meego Wiki
Views

Quality/QA-tools/OTS/DeveloperDocs/Behaviour

From MeeGo wiki
< Quality | QA-tools | OTS | DeveloperDocs
Revision as of 15:17, 4 January 2011 by Tgalvin (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

OTS Behaviour

States

An OTS exhibits system wide stateful behaviour that is visible in the course of a run.

A Task holds the state in the Distributor. Intimately linked to this there is a simple state machine in the Worker which cycles around a two state system.


Worker

1. The Worker goes into a Started State on receipt of a CommandMessage. At this point it sends a The StateChangeMessage to the Response Queue with the Start Condition.

2. When the Task has finished Running the Worker is back in the Finished State, this State Change is communicated via a State Change Message via a Finish Condition.


WorkerStates.jpg

Tasks

The States Changes of the Tasks are triggered by Conditions that communicated by a special DTO The StateChangeMessage.

TaskStates.jpg

Personal tools