You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you planning tu support CBOR? Or, if I went for implementing it, could you please give me a little guidance what to implement? I'd naturally look into how JSON or XML import/export is implemented and write a similar code for CBOR. Are there any caveats which I should watch out for?
Thank you for all your help.
Maria
The text was updated successfully, but these errors were encountered:
No, we have no plans for supporting CBOR and instead we have our own LYB binary format. We have decided this way mainly because of the CBOR requirement for a global mapping file of schema nodes to integers (but LYB has its problems as well).
So, my advice would be to carefully think about the design with regard to the schema node identifiers. Specifically, how to handle modules with no found mapping. You could refuse to print such a module but one often works with non-standardized modules, from drafts or vendors, so it does not seem like an acceptable solution. I would provide more input once you have basic use-cases working and a PR in libyang created.
Hello!
Are you planning tu support CBOR? Or, if I went for implementing it, could you please give me a little guidance what to implement? I'd naturally look into how JSON or XML import/export is implemented and write a similar code for CBOR. Are there any caveats which I should watch out for?
Thank you for all your help.
Maria
The text was updated successfully, but these errors were encountered: