[riot-notifications] [RIOT-OS/RIOT] doc/memos: RDM Runtime Configuration Architecture (#10622)

José Alamos notifications at github.com
Tue Jan 15 11:14:50 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
+[storage facilities](5-storage-facilities). 
+
+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)

> To convince the reader that the homework has been done and this is the best solution.

Why do you consider this to be necessary? Why do you think is necessary to convince the reader this is the best solution?

It's sort of expected the RDM will consider the best efforts solution, right? (It's hard to confirm this is THE BEST solution but it's the best we could do)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10622#discussion_r247832245
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190115/05b0ad50/attachment.html>


More information about the notifications mailing list