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
Looking to get packed encoding support added. I use CBOR to save cached OCR data
the file is around 8.6mb which is around 50% smaller than the JSON equivalent. Reading the cbor file in a hex editor shows a lot of stuff are repeated like field names/certain fields that repeat the same value over and over.
Packed encoding would be wonderful 😄
Acceptance Criteria
Works
Smaller file size
Suggestions for a technical implementation
No response
The text was updated successfully, but these errors were encountered:
Would love packed encoding. We are trying to use ciborium to communicate with a microprocessor and we need to use integer based field names, payloads are 10x smaller this way.
Additionally, integer based names are helpful for evolution of schemas over time - for example, take a look at how minicbor_derive works. By using integers for names, fields can be renamed in code without breaking binary compatiblity (much like protobufs/flatbuffers).
Is there an existing issue for this?
Description
Looking to get packed encoding support added. I use CBOR to save cached OCR data
the file is around 8.6mb which is around 50% smaller than the JSON equivalent. Reading the cbor file in a hex editor shows a lot of stuff are repeated like field names/certain fields that repeat the same value over and over.
Packed encoding would be wonderful 😄
Acceptance Criteria
Suggestions for a technical implementation
No response
The text was updated successfully, but these errors were encountered: