String serialization for standard data types
To be combined with state sharing using some message sharing service.
Comments (8)
-
reporter -
reporter Going with JSON. It is far simpler than YAML, more portable. And all valid JSON is valid YAML anyway, provided the text uses unique keys in arrays of key-value pairs.
-
reporter Underway as of bc492b27d4da5b7888c0ca47cb9287a9ff514edc
-
reporter Implemented basic infrastructure as of 87d0085157055d1b5476007b9508ed5901b9b364
-
reporter Most types serialized by 94b743acf15a488772d30fe808547080a8daa794
-
The end goal here from the storage perspective is to have a function to call that will return a JSON object or serialized string for static and (separately) dynamic data, for each simulated robot. Once that's available, real-time streaming to the web interface will fall right into place.
-
reporter There is a nice example in applications-web//scl_redis_serv_puma
-
reporter - changed status to resolved
Works as of 14d4963
- Log in to comment
For JSON : jsoncpp (https://blog.thousandeyes.com/efficiency-comparison-c-json-libraries/) seems like the best bet For YAML : yaml-cpp (https://code.google.com/p/yaml-cpp/wiki/HowToEmitYAML) is quite intuitive