From Wikipedia : According to RFC 6838 (published in January 2013 : https://www.rfc-editor.org/rfc/rfc6838), any use of types in the “x.” tree is strongly discouraged. Media types with names beginning with “x-” are no longer considered to be members of this tree since January 2013. Then use directly application/msgpack
In general the important question is which client will receive the serialized objects – browsers/JavaScript engines like (node-js), Java client, unknown/multiple clients. JSON – JSON syntax is basically JavaScript and therefore any component with a JS engine will handle its parsing very well – even complicated data-structures will be converted to “living” objects efficiently. JSON … Read more
Json human readable/editable can be parsed without knowing schema in advance excellent browser support less verbose than XML XML human readable/editable can be parsed without knowing schema in advance standard for SOAP etc good tooling support (xsd, xslt, sax, dom, etc) pretty verbose Protobuf very dense data (small output) hard to robustly decode without knowing … Read more