On Monday 09 March 2015 09:17:26 Lankswert, Patrick wrote: > Uze, > > I would suggest starting with the CBOR RFC > (http://tools.ietf.org/html/rfc7049). The objectives section provides a > nice introduction to all of Thiago's points.
Again, I need to ask: are we talking about API or are we talking about transmitting that on the wire? Or both? If we're talking about the wire, then I'd say we should encode the request in an array or object according to what we're already encoding on the wire. If we're sending JSON on the wire, then we use JSON. If we switch to CBOR, then we send CBOR. Just as long as we don't mix. If we're talking about API, then neither JSON nor CBOR are a good idea. That should just be a structured type or more parameters in the function call. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 173 bytes Desc: This is a digitally signed message part. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150309/64fb6fc3/attachment.sig>
