Ichthyostega
72258c06bd
The problem with passing the deadline was just a blatant symptom that something with the overall design was not quite right, leading to mix-up of interfaces and implementation functions, and more and more detail parameters spreading throughout the call chains. The turning point was to realise the two conceptual levels crossing and interconnected within the »Scheduler-Service« - the Activity-Language describes the patterns of processing - the Scheduler components handle time-bound events So by turning the (previously private) queue entry into an ActivationEvent, the design could be balanced. This record becomes the common agens within the Scheduler, and builds upon / layers on top of the common agens of the Language, which is the Activity record. |
||
|---|---|---|
| .. | ||
| activity-detector-test.cpp | ||
| activity-detector.hpp | ||
| block-flow-test.cpp | ||
| scheduler-activity-test.cpp | ||
| scheduler-commutator-test.cpp | ||
| scheduler-invocation-test.cpp | ||
| scheduler-load-control-test.cpp | ||
| scheduler-service-test.cpp | ||
| scheduler-stress-test.cpp | ||
| scheduler-usage-test.cpp | ||
| work-force-test.cpp | ||