Compactness of messages is important, but it is also important (to me at
least) to be realizable in an implementation with limited resources,
such as embedded devices in what are now popularly called "M2M"
applications. A lot of these devices could use IP all the end to end,
but may have a very compact, simple stack and applications (i.e. no
browser). Is JSON typically implemented when there is no browser?
Would it be hard to do in a resource constrained device (i.e. where we
talk about memory size in Kilo-bytes still).
Thanks
Ben
We had a discussion on XML vs. JSON. I prefer the one with most compact
messages.
On vCard and JSON: what is the status of "A JavaScript Object Notation (JSON)
Representation for vCard"?
http://tools.ietf.org/html/draft-bhat-vcarddav-json-00
On valid times: can we use same format as certificates? They have similar simple
requirements: valid notBefore& notAfter.
http://tools.ietf.org/html/rfc3280#section-4.1.2.5
Teco
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws
