[riot-notifications] [RIOT-OS/RIOT] doc/memos: RDM Runtime Configuration Architecture (#10622)
notifications at github.com
Wed Jan 9 11:28:19 CET 2019
jia200x commented on this pull request.
> +[configuration manager](4-configuration-manager) and the
+[RIOT Registry](3-the-riot-registry) and its sub-components:
+one or more [Registry Handlers](4-registry-handlers) and one or more
+A RIOT Application may interact with the Configuration Manager in order to
+modify access control rules or enable different communication interfaces.
+Also, it may interact with the RIOT Registry directly if it's
+required to load/store a persistent configuration.
+!(./files/rdm-draft-alamos-lanzieri-runtime-configuration-architecture/architecture.svg "Runtime Configuration Architecture")
+# 3. The RIOT Registry
+The RIOT Registry is a module for interacting with
+**persistent key-value configurations**. It's heavily inspired in the
+[Mynewt Config subsystem](https://mynewt.apache.org/latest/os/modules/config/config.html)
After an extensive research with @leandrolanzieri, we found this architecture to suit our needs because:
- It's module and storage agnostic
- Security can be added on top
- It's extremely modular.
- It's well tested in Mynewt and Zephyr, so there shouldn't be big surprises with the implementation
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications