eclipse-score / eclipse-score/lifecycle
Create a design for using mw::com for alive notification reporting
- Dominant language
- C++
- Stars
- 6
- Forks
- 34
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 80
Description
The design should include:
* Integration of mw::com on the application-side
* Integration of mw::com on the launch_manager-side
* Cross-cutting concerns
* Configuration of the communication
* How to handle the case when ipc channel overflows? I.e. too many checkpoints reported
* Security
* How to make sure only the correct process can access the ipc channel?
* How can we be sure within the launch_manager that the correct process reported the alive notifications?
* Performance / Resource consumption
* What are the required resources on the application side (e.g. threads, memory, etc)
* What are the required resource within the launch_manager?
* How to fine-tune resources? E.g. setting the shared memory size
* Open issues using mw::com
* What are feature requests to mw::com we should communicate?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.