openstack/taskflow
Code Issues Proposed changes

Put semantics preservation section into note block

Browse Source 
Change-Id: I2fceb1628ef384f6d5db1f292cabe48195efbf9c
This commit is contained in:
Joshua Harlow 2015-04-04 19:45:33 -07:00
parent fd58fd8bb6
commit ebc0782868
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/engines.rst
View File

@ -17,11 +17,13 @@ and *ideal* is that deployers or developers of a service that use TaskFlow can
select an engine that suites their setup best without modifying the code of
said service.
Engines usually have different capabilities and configuration, but all of them
**must** implement the same interface and preserve the semantics of patterns
(e.g. parts of a :py:class:`.linear_flow.Flow`
are run one after another, in order, even if the selected engine is *capable*
of running tasks in parallel).
.. note::
Engines usually have different capabilities and configuration, but all of
them **must** implement the same interface and preserve the semantics of
patterns (e.g. parts of a :py:class:`.linear_flow.Flow`
are run one after another, in order, even if the selected
engine is *capable* of running tasks in parallel).
Why they exist
--------------