SDRP — ControllableController ambiguity

Problem: The start() and stop() operations introduce the following
ambiguity: What can a client expect the first time start() is called vs.
calling start() after a stop() call? Is the component put in a known
state every time start() is called, or does it simply resume its
operation from the point where is received a stop(). In other words, the
semantics of the start->stop->start transition are ill-defined.

Proposed Solution:

Add a resume() operation to the interface to resolve this ambiguity.
Resume() would indicate that the component should continue its operation
from the point where stop() was issued. Start() would indicate that
component should be placed back in an "initial" state (at a point after
the LifeCycle::init() for components).

No Data Available