This central operation sits at a crossroad and is used - from external clients to fed new work to the Scheduler - from Workers to engage into execution of the next Activity - recursively from the execution of an Activity-chain From these requirements the semantics of behaviour can be derived regarding the GroomingToken and the result values, which indicate when follow-up work should be processed |
||
|---|---|---|
| .. | ||
| activity-detector-test.cpp | ||
| activity-detector.hpp | ||
| block-flow-test.cpp | ||
| scheduler-activity-test.cpp | ||
| scheduler-commutator-test.cpp | ||
| scheduler-invocation-test.cpp | ||
| scheduler-usage-test.cpp | ||
| work-force-test.cpp | ||