Our tag-length-value use case is to unpack binary messages from IoT sensors, specifically data sent over LoRaWAN. Many sensors use a tag-value structure, where the length isn't encoded in the message. Eg the tag 0x01 is associated with a 4-byte unsigned integer and tags 0x02 and 0x03 are 1-byte unsigned integers, etc.
I'm considering using your library as a starting point, but extending it with support to change endianness and different sizes of integers (eg by using the struct module). Does that sound like a good plan, and if so, would you consider adding this support if we provide the patches?
Our tag-length-value use case is to unpack binary messages from IoT sensors, specifically data sent over LoRaWAN. Many sensors use a tag-value structure, where the length isn't encoded in the message. Eg the tag 0x01 is associated with a 4-byte unsigned integer and tags 0x02 and 0x03 are 1-byte unsigned integers, etc.
I'm considering using your library as a starting point, but extending it with support to change endianness and different sizes of integers (eg by using the struct module). Does that sound like a good plan, and if so, would you consider adding this support if we provide the patches?