Archived
Thiago Macieira
4a99af92dc
It's very easy for a short packet to contain a very high number of nested arrays (a packet with N bytes can be N-1 nested arrays), which could cause stack overflow problems in devices using cbor_value_map_find_value, so ensure that we won't crash. The actual value needs to be chosen by the implementor depending on the stack size of their devices and the expected usage. Signed-off-by: Thiago Macieira <thiago.macieira@intel.com>
26 lines
843 B
Plaintext
26 lines
843 B
Plaintext
==== To Do list for libcbor ====
|
|
=== General ===
|
|
* API review
|
|
* Benchmark
|
|
* Write examples
|
|
** Simple decoder
|
|
** Decoder to JSON
|
|
** Windowed encoding/decoding (limited memory)
|
|
|
|
=== Encoder ===
|
|
* Write API docs
|
|
* Add API for creating indeterminate-length arrays and maps
|
|
* Add API for creating indeterminate-length strings
|
|
* Add API for relaxing doubles to floats and to integers
|
|
* Add length-checking of the sub-containers (#ifndef CBOR_ENCODER_NO_USER_CHECK)
|
|
* Decide how to indicate number of bytes needed
|
|
** Suggestion: return negative number from the functions
|
|
|
|
=== Decoder ===
|
|
* Write functions not yet implemented
|
|
* Add API for stream-decoding strings
|
|
* Add API for checking known tags and simple types
|
|
* (unlikely) Add API for checking the pairing of a tag and the tagged type
|
|
* Write tests for error conditions
|
|
* Fuzzy-test the decoder
|