Consider changeing de/serialization support away from Postcard
quietlychris opened this issue · comments
postcard has been more difficult to work with that expected. It was primarily chosen to accommodate directly sending/receiving messages with embedded systems due to out-of-the-box #![no_std] support. However, as mentioned, the process of working with the de/serialization functions has been more difficult than expected, and certain behaviors are occurring during that process that have been difficult to track down. In the future, it might be a good option, but since this middleware is primarily intended to start with support for embedded Linux and other systems with the standard library available, it may make more sense to switch to something like bincode
A good, although somewhat dated, overview of Rust de/serialization frameworks can be found at https://blog.logrocket.com/rust-serialization-whats-ready-for-production-today/
Postcard has hit 1.0 with a stable wire format and the issues that came up have pretty much all been resolved.