Sorry for belated response. > On Jan 30, 2016, at 2:34 PM, Sterling Hughes <[email protected]> wrote: > > > > On 1/29/16 6:25 PM, marko kiiskila wrote: >> Hi all, >> >> I was not happy with my first attempt at the interface between config and >> subsystems. >> So here’s a 2nd version. >> >> ... >> >> There is still no persistent storage of config. We should have at least 2 >> options for this: >> storage of config in files, or in a raw flash region (when FS is not >> available). >> I’m thinking the API should be similar for both, so decision of which one to >> use will be >> a simple build time knob. >> > > +1 to this. > > How does configuration get registered with the system? i.e. If I wanted to > dump the current state of all configuration in the system, how would that > happen using the above APIs?
That would be through the commit(). If you’re trying to persist data, it would go to your persistent storage of choice. If you’re trying to view it, it would come out to console or somewhere else. > Should commit() have the notion of a commit ID + timestamp? That way for a > given set of variables, you can know when they were changed. You could build it into persistent storage interface, if deemed necessary. — M
