concise-encoding
concise-encoding copied to clipboard
kstenerud
The secure data format for a modern world
Stumbled upon your project on today's Ask HN. It may be too much trouble for too little gain, but something I've had to deal with in recent years that has...
The [spec](https://github.com/kstenerud/concise-encoding/blob/master/cbe-specification.md#variable-width) indicates the encoding is `[type] [length] `, where `length` is an unsigned LEB128. However, since unsigned LEB128 is also variable-width, how would a binary parser tell when `length`...
I can't see how the separation of those types is useful.
I spent last few days digging around why would such an innocently looking feature be left as a TODO. I was looking for something to put my hands into, and...
Currency amounts are a common use case for APIs. In a typical JSON implementation, you often see something like: `{"amount": 5.00, "currencyId": "USD"}` ^ This is incorrect, since most parsers...
I would appreciate if you would share your rationale for CE's design choice(s) regarding extensibility (or lack thereof). What research have you done with regards to extensibility? Have you looked...
Right now, there are separate length=0 arrays for each numeric type (int8, uint16, int16, etc). Since all numeric types in CE are considered equivalent, aren't all numeric arrays with 0...
I've mostly finished my implementation of the CE temporal types, and there are a number of points where the spec seemed ambiguous, so I used the empirical behavior of `enctool`...
After a certain point, enctool kind of gives up trying to handle years, and just latches on to a particular value: ``` $ echo 'c1 1000000000000000000000000000000-1-1'|./enctool convert -df cbe|hexdump -C...
I tried making a 2500-character integer (in CTE) and sending it to enctool. It happily made a >1KB CBE document. Then when I tried parsing that CBE with enctool, it...