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

danpetry notifications at github.com
Tue Jan 8 19:25:46 CET 2019

danpetry requested changes on this pull request.

> +
+A runtime configuration system is in charge of providing a mechanism to set and
+get the values of configuration parameters that are used during the execution
+of the firmware, as well as a way to persist these values. Runtime
+configurations are deployment-specific and can be changed on a per node basis.
+Appropriate management tools could also enable the configuration of node
+Examples of runtime configurations are:
+- Transmission duty cycles
+- Sensor thresholds
+- Security credentials
+- System state variables
+These parameters might have constraints, like a specific order to be applied
+(due to interdependencies) or value boundaries.

Should an application programmer NOT set and expose any config parameters which are part of a different module, to avoid conflicts? Worth stating this? I.e "any parameters changed by a RH or SF, either directly or indirectly, MUST only belong to the RH/SF's module"?

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/20190108/99765a9c/attachment-0001.html>

More information about the notifications mailing list