<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>* LLSD is just awful - a hodgepodge compromise between doing the old thing and doing the right thing. Let's _please_ stay well clear of that.<BR>
* JSON is really really cool for browser-oriented apps, but is there a schema for it?<BR>
* XML is XML. Industry standard, well proven, and actually has stuff like XML Schema, which is what you'd use to add type information to data; schema or not, the serializer infers type from the serialized class.<BR><BR>
We at Tribal are using a Serialized Command Object approach, where we POST XmlSerialized "Command Objects", which can reference any other serializable type. Kind of an Ultralight Web Service. Easy as pie to produce output, and a pice of cake to parse it. Not any more wordy than what's needed to have human-readable datagrams with extensible semantics.<BR>
<BR>
Works like a charm.<BR>
<BR>
I believe this approach is part of what MW talked about in his posts on services from a while back.<BR>
<BR>
/Stefan<BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Tue, 13 May 2008 19:25:55 +0200<BR>> From: DrScofield@xyzzyxyzzy.net<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: [Opensim-dev] what to use for serializing structures? LLSD? XmlSerializer? JSON?<BR>> <BR>> hi,<BR>> <BR>> we are currently looking at adding REST support to the RemoteAdmin <BR>> plugin (other stuff to follow) --- the idea being that we can get <BR>> information about (as well as change state of) a running OpenSim <BR>> instance not only via XmlRpc but also via REST.<BR>> <BR>> looking at the way we currently deal with serialization we either<BR>> <BR>> * use LLSD where mandated by secondlife (e.g., CAPS)<BR>> * use System.Xml.XmlSerializer<BR>> * use XmlRpc serialization (which goes back to System.Xml)<BR>> <BR>> LLSD is being used by linden lab's and is proposed by LL/SLAWG as the <BR>> serialization protocol of choice (IIUC). in my opinion it suffers from <BR>> being a bit verbose and not really easy to parse.<BR>> <BR>> XmlSerializer is "built in". on the other hand it's wordy and more <BR>> complex to parse; also, it doesn't distinguish between the number 4711 <BR>> and the string "4711" --- you have to know that a certain tag contains a <BR>> string (or a number).<BR>> <BR>> JSON is lean, and easy to use from AJAX apps as well as python scripts <BR>> (and the likes). it requires an additional DLL. it does however <BR>> distinguish between strings and numbers. using a library like <BR>> jsonexserializer (http://code.google.com/p/jsonexserializer/ --- BSD <BR>> license) makes it easy to use from C#.<BR>> <BR>> personally, i've started to like JSON because it's lean and easy to use <BR>> --- but i'd like to hear from you guys what you think about this.<BR>> <BR>> cheers,<BR>> dr scofield<BR>> <BR>> -- <BR>> dr dirk husemann, mathmatics and computer science, ibm zurich research lab<BR>> SL: dr scofield ---- drscofield@xyzzyxyzzy.net ---- http://xyzzyxyzzy.net/<BR>> RL: hud@zurich.ibm.com - +41 44 724 8573 - http://www.zurich.ibm.com/~hud/<BR>> <BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>