-
Notifications
You must be signed in to change notification settings - Fork 6
Home
It is a framework for the reactive firmware - it solves concurrency by eliminating it.
Every firmware has two requirements: it is reactive when user has to input, when there's connectivity or any randomly generated events; and it is real time, when acquiring, processing and actuating in the environment.
It is the react.o's author view that it does make a lot of sense to formally apply the reactive paradigm in firmwares considered that there must be mechanism for the real time requirements. That's what react.o is - a framework to provide reactive firmware design with support for real time tasks.
It is a Main Loop, with multiple Event Queues where Handlers are connected to process events. Complex data paths are simplified, concurrency is minimized while parallelism boosted and worst case real-time scenario is easier to estimate.
react.o is/has:
- Portable
- Deferred Work
- Fast and Small
- Deterministic
- Reusable containers
More info: https://flplv.github.io/reacto/