Comments on: which serialization format for OpenSim REST services?

By: Gareth Nelson

Gareth Nelson — Sat, 17 May 2008 19:15:14 +0000

I just ran into this post by chance........

LLSD wins hands down, why have more formats than needed?

By: Kyle H

Kyle H — Wed, 14 May 2008 13:42:56 +0000

I’ve sent my message to opensim-dev in support of JSON, for reasons which relate partially to “how expensive is it to transmit XML? how expensive is it to parse XML?” I also like your point that JSON distinguishes between 4711 and “4711″.

Really, a representation language that can be described in 5 state diagrams is much better than the huge and overspecified cruft from the W3C. Regardless of the fact that there’s a documented interface to parse it, how many times have the XML parsers been found to have bugs?

By: Mo Hax

Mo Hax — Wed, 14 May 2008 12:00:23 +0000

Hate to be the wet blanket, but Agile places the burden of 'proof' on JSON to show that adding yet another tech to the OpenSim code base is worth it, not matter how simple and cool it is.

What is it going to be used for? Who's the customer? People coding administrative front ends? Does this have any chance of growing into something more, like a way to query or add serialized assets?

JSON seems obvious if this is just for administrative front end mashups. Maybe we limit the scope to that and make it JSON.

LLSD would be my pick for asset serialization and such since it is more largely compatible with LL and the working group and includes three forms, xml, binary, and 'human readable', which I think is the one you are comparing JSON with.

I suppose nothing wrong with having right tool for the job, and little mashes up better than JSON. But overall I prefer using what we have.