<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Ok, next time, I'll half the dose of that cough syrup.<BR>
<BR>
Aaanyway : I still think it's a REALLY bad idea to put forward as a 'standard region API' something that is more application-and-environment specific (JSON) when there is something that is less application-and-environment specific (XML)<BR><BR>Is there a concrete win with Json over Xml that I'm missing?<BR><BR>
Everything else aside, I'm for us standardizing on _one_ text protocol and _one_ binary protocol (if needed); otherwise we're sinking deeper into our own little version of UDP-XmlRpc-CAPS-LLSD-Whatevercomesnextmonth mayhem.<BR>
<BR>
And, it would be great if the api was formulated as a set of abstract classes, interfaces and event hooks, so however you decide to implement the protocol layer, somebody else could implement it differently. (SOAP, anybody?)<BR>
<BR>
That would ROCK. :D<BR>
<BR>/Stefan<BR>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
From: stefan@tribalmedia.se<BR>To: opensim-dev@lists.berlios.de<BR>Date: Wed, 14 May 2008 08:55:21 +0200<BR>Subject: Re: [Opensim-dev] what to use for serializing structures? LLSD? XmlSerializer? JSON?<BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
<BR><BR><BR><BR>
<HR id=EC_stopSpelling>
> Date: Wed, 14 May 2008 08:18:42 +0200<BR>> From: DrScofield@xyzzyxyzzy.net<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] what to use for serializing structures? LLSD? XmlSerializer? JSON?<BR>> <BR>> Stefan Andersson wrote:<BR>> > * LLSD is just awful - a hodgepodge compromise between doing the old <BR>> > 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 <BR>> > schema for it?<BR>> there is at least a grammar for it: www.json.org, right on the front page.<BR>> > * XML is XML. Industry standard, well proven, and actually has stuff <BR>> > like XML Schema, which is what you'd use to add type information to <BR>> > data; schema or not, the serializer infers type from the serialized class.<BR>> true.<BR>> ><BR>> > We at Tribal are using a Serialized Command Object approach, where we <BR>> > POST XmlSerialized "Command Objects", which can reference any other <BR>> > serializable type. Kind of an Ultralight Web Service. Easy as pie to <BR>> > produce output, and a pice of cake to parse it. Not any more wordy <BR>> > than what's needed to have human-readable datagrams with extensible <BR>> > semantics.<BR>> > <BR>> > Works like a charm.<BR>> > <BR>> > I believe this approach is part of what MW talked about in his posts <BR>> > on services from a while back.<BR>> ok. will have to look that up then.<BR>> <BR>> considering that we are looking into this from a REST angle for external <BR>> control applications, i'm still leaning towards JSON: easy to do AJAX <BR>> interface, easy to use from python (and other scripting languages).<BR>> <BR>> but let's see what else we'll get regarding opinions. so far i've <BR>> collected 5 votes on <BR>> http://xyzzyxyzzy.net/2008/05/14/serialization-format-for-opensim-rest-services/ <BR>> ;-)<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></BLOCKQUOTE></body>
</html>