Hi:
Correct me if I'm wrong but I think that JSON.NET most famous
serializer/deserializer (http://json.codeplex.com/) works like
standard .NET XML serializer...
The advantage of using JSON is less storing space and some thing like
direct connection with Javascript. If the first is not a problem
I use OSDMap / json exclusively in projects. Encoders and decoders for
python and php work very well, and it is very easy to work with inside the
region modules. Very clean and efficient, overall. Since we have OSDMap and
friends to help on the OpenSim side, I think it would makes sense to
The libomv OSD classes handle it in OpenSim, which as far as I can tell is
the generic name given to the libomv LLSD handler.
BlueWall
On Mon, Jul 5, 2010 at 5:01 AM, Impalah Shenzhou impa...@gmail.com wrote:
Hi:
Correct me if I'm wrong but I think that JSON.NET most famous
I'm not against JSON (I use it on web projects), but I don't know how
much work will require to convert XML serializing code to JSON.
If this were a vote, mine will be abstention.
Greetings
2010/7/5, BlueWall Slade bluewall.sl...@gmail.com:
The libomv OSD classes handle it in OpenSim, which
Not a whole lot of feedback here yet, maybe people are on a long
weekend type camping vacation..
I'm partial to OSD/json, myself.I'd also like to, at some point,
get a version number in there along with a definition of the format
for people who want to write integration tools..however,
Having just worked on a JSON project myself internally - I personally developed
a bit of a loathing for the format. I'm personally partial to XML, ideally with
a corresponding DTD.
Adam
-Original Message-
From: opensim-dev-boun...@lists.berlios.de [mailto:opensim-dev-
If it's using the OSD serialization methods in libomv, then there are
several serializations available, including XML, JSON, and a binary format.
I've used all three in projects and I've found the XML to be the most robust
and mature. Depending on the version of libomv included with OpenSimulator,
