You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JSON was chosen because it’s very easy to work with and is human readable.
Protocol buffers are more efficient and do provide typing it’s harder to update the format because you need the protocol schema at both ends.
For RSMP 4 we’re considering CBOR, which is a binary encoding of JSON. It’s more efficient, but with the flexibility of JSON, and it does not require a protocol schema.
We do work with JSON schemas to validate the format of messages. Whether it would be easier to work with a protocol schema is worth considering.
When you're communicating in JSON, you may also want to consider whether or not to compress it. Compression can reduce the size of the message by up to 75%. Is it worth looking into?
Question from a manufacturer:
Did anyone used Google protobufs for validating messages and stronger message typing when using RSMP protocol?
The text was updated successfully, but these errors were encountered: