-
Yuya Nishihara authored
This can avoid complicated state handling in future implementation. If CmdAgent waits for worker ready, it needs to distinguish running/waiting/new state of the first session because: - it starts the first session (=waiting) on CmdWorker.Ready - and it needs to abort the first session on CmdWorker.Terminated, if the first session is not started yet (=waiting) - but it should do nothing on CmdWorker.Terminated, if the first session (=running) was dequeued just before termination - but it needs to reschedule the first session on CmdWorker.Terminated, if the first session is added (=new) after termination request In contrast, CmdSession can simply start on Ready and abort on Terminated. Also, it can represent waiting/running state with no modification.
6332a83c96f0