Hi Jakub, On Wed, 2019-06-05 at 15:01 +0200, Jakub Witowski wrote: > Netwrk keys, application keys and elements with models have been > simplified in json storage file. Arrays objects are no longer > required. > > Jakub Witowski (3): > mesh: Refactor elements related object in json file > mesh: Refactor net keys related object in json file > mesh: Refactor app key related object in json file > > mesh/mesh-db.c | 469 ++++++++++++++++++++++++++--------------------- > -- > 1 file changed, 248 insertions(+), 221 deletions(-) > The proposed change would be okay if not for the fact that we plan to re-use the same code for storing the information database for provisioner/configuration client. That puts constraints on the format in which the json data is stored. However, since mesh-db.h describes self-contained API, it should be easy to create a custom bluetooth-meshd solution, i.e., keeping the mesh-db APIs unchanged, but use customized routines to implement them. That should allow you to keep local node configuration in your own format. Best regards, Inga
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
