News for hackers. Stuff that matters.

A comment on Son – A minimal subset of JSON for machine-to-machine communication. Parent comment

Re:Son – A minimal subset of JSON for machine-to-machine com... by RodgerTheGreat on Tuesday March 14, 2017 @03:50PM (#13870879)
How about Bencode[1], the data format used in Bittorrent? Values and encodings are already bijective, the format is extremely simple and it's already standardized and described. The only feature "SON" has which Bencode doesn't support is floating-point values, and as you imply above they are very likely to be mutilated in JSON or a subset thereof.

[1] https://en.wikipedia.org/wiki/Bencode

[ Parent | on HN ]
Re:Son – A minimal subset of JSON for machine-to-machine com... by seagreen on Tuesday March 14, 2017 @06:26PM (#13872055)
This is the second time Bencode's been mentioned in the context of Son. I didn't know about it before, it definitely looks interesting! However if you're sending data to a service that only accepts JSON then it's obviously not an option.
[ Parent | on HN ]
Re:Son – A minimal subset of JSON for machine-to-machine com... by RodgerTheGreat on Tuesday March 14, 2017 @06:29PM (#13872075)
Fair enough. Backwards compatibility is useful in some contexts.
[ Parent | on HN ]
Re:Son – A minimal subset of JSON for machine-to-machine com... by seagreen on Tuesday March 14, 2017 @07:26PM (#13872495)
By the way, I love that Bencode is bijective. That's a really nice property for a serialization format, and even though I don't mention it on the README it's one of the goals of Son.
[ Parent | on HN ]