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

José Alamos notifications at github.com
Wed Jan 2 14:39:51 CET 2019

jia200x commented on this pull request.

> +
+The configuration manager MAY provide an access control mechanism for
+restricting access to the configurations. However, it can relay on security
+implemented on the layers mentioned above (e.g CoAP and DTLS, CHAP on PPP, etc)
+# 7. RCS Usage Flow
+1. Modules declare and register **registry handlers** for configuration groups
+in the RIOT Registry.
+2. **Storage facilities are registered** as sources and/or destinations of configurations in the RIOT Registry.
+3. The RIOT Registry is initiated. All configuration parameters are loaded from the sources with the Storage interface.
+4. For each loaded parameter, a configuration group that contains that parameter is searched for. If found, the corresponding `set` handler is called with the current parameter and value.
+5. The `commit` handler is called once all configurations have been loaded from the registered sources.

yes, I think that's the proper concept.

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...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190102/626ae653/attachment.html>

More information about the notifications mailing list