- Runtime "configuration" system naming
Re: Runtime "configuration" system naming
toggle quoted messageShow quoted text
Thanks for the feedback.
I did think about using “marshalling”, but I thought it was less common than “serialization” so I went for the “s11n” abbreviation.
I would really like to keep it short if possible
From: Erwan Gouriou <erwan.gouriou@...>
Sent: 27 March 2018 15:30
To: Cufi, Carles <Carles.Cufi@...>
Subject: Re: [Zephyr-devel] Runtime "configuration" system naming
Serialization is also sometime called marshalling, so an alternative could be "marshal"/"cfg_marshal"/"rtcfg_marshal"
On 27 March 2018 at 14:51, Cufi, Carles <Carles.Cufi@...> wrote:
Andrzej from Nordic has just ported the *run-time* configuration system from Mynewt into Zephyr .
This is essentially a system-wide way of loading and storing all state from and to non-volatile memory (i.e. flash) in a completely centralized way.
Since it serializes the data before storing it (and deserializes it after loading), and we already use the word "config" for *compile-time* configuration, we have currently renamed it to "s11n" (for serialization).
But some people find this name confusing, so I am now addressing a wider audience for feedback.
The currently proposed names are:
Any preferences or alternatives?
Zephyr-devel mailing list
Join firstname.lastname@example.org to automatically receive all group messages.