Skip to content

Pause/Resume improvements #296

Closed
Closed
@sobychacko

Description

@sobychacko
          I think it would be more consistent and easier to follow if we instead do pause/resume exactly how start/stop is currently implemented. This would also remove the need to attempt to use the lifecycleMonitor in the subclass. 

Basically, we would have an abstract doPause()/doResume() where the concurrent does the 1-N delegation call to its child containers and each child container then does the work to pause/resume (as you have it now).

Originally posted by @onobc in #292 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions