WIP: Mode Tree #130
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "mode-tree-init"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue: #15
The mode tree components generally consist of three abstraction/problem groups:
Actually, some of the changes and new features introduced here should be applied to other problem domains like Actions or HK as well. This includes a reply scheme because now every request has to be one that is acknowledged and needs explicit generation of verification telemetry.
In that sense, we still require something similar to the commanding service base, where active requests are tracked and which performs the full verification completion so that the end consumers of these requests don't need to worry about that as well. Incidentally, we can probably decouple those end consumers from PUS1 completely, which is probably better from an architecture point of view. I'd like to still have some way to report step success/failures for actions specifically, but special consideration for the ActionRequest should do the job as well.
Pull request closed