[riot-notifications] [RIOT-OS/RIOT] doc/memos: RDM Runtime Configuration Architecture (#10622)
notifications at github.com
Tue Jan 15 11:26:59 CET 2019
danpetry 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)
> It's sort of expected the RDM will consider the best efforts solution, right?
Yep that sounds reasonable. You could include a reference to Zephyr as well? At the moment it reads like you copied MyNewt and didn't look at anything else
> Why do you consider this to be necessary? Why do you think is necessary to convince the reader this is the best solution?
I raised a question, as a point of discussion - happy with however it's resolved. Could you please wait until review points have been resolved via discussion with the reviewer before resolving conversations? As I mentioned, always happy to discuss if you disagree with any points.
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