Re: [mmox] XML serialization

Jon Watte <> Wed, 25 February 2009 01:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 81A953A6928 for <>; Tue, 24 Feb 2009 17:36:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2zq4vKDAD0ND for <>; Tue, 24 Feb 2009 17:36:53 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id A85E23A67EF for <>; Tue, 24 Feb 2009 17:36:52 -0800 (PST)
Received: by with SMTP id 5so2611601ywh.49 for <>; Tue, 24 Feb 2009 17:37:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=EEo3evrsMU58qfU7R54ti0DYVni565DsWdv66Ek7SLM=; b=A97vdwhhVe3Pd6aoWsQkKMt3G34J7r41FhqDRc4brzBKwo1pxHCKzb5jRw72kM9FwI FxuuzrzBPmswRvQ+mHSsk3nIVx02kXlmeSwMzKXuzixO4jSp/BLfnBBmvy7Yjp1PFtVR IAAKrLgwbEs2wm7Uny0yc08p43acXL1URgB6E=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=qKKY5lRIczKTnCCCntUHaWDe5jYNEqvVhfKek5QVKKURw7VDFQhNSNSE9XtobgDuGP JRA2xT9Un+mdVZqXwnyeGS1Krpy87WwXplS6eQgeShBJgES5pJJ/akhKUv1S+rGoVsdz iLIOQ5Dy8o5scadjM2PzS7Pyhp17Osq73atzw=
Received: by with SMTP id g1mr190474and.106.1235525831195; Tue, 24 Feb 2009 17:37:11 -0800 (PST)
Received: from ? ( []) by with ESMTPS id d38sm10511512and.49.2009. (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 24 Feb 2009 17:37:10 -0800 (PST)
Message-ID: <>
Date: Tue, 24 Feb 2009 17:37:08 -0800
From: Jon Watte <>
User-Agent: Thunderbird (Windows/20081209)
MIME-Version: 1.0
To: "Meadhbh Hamrick (Infinity)" <>
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [mmox] XML serialization
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 25 Feb 2009 01:36:54 -0000

Meadhbh Hamrick (Infinity) wrote:
> it sounds like you want to do some processing at points "b" and "c". 
> after it has been received by the transport and before it gets 
> un-marshalled / de-serialized.

Yes. In fact, my system may actually use the XML directly, without 
de-marshaling. The whole point of a data representation is that it is 
useful as-is, IMO :-)

> and also... is this a requirement of your system? or just the way that 
> seems right to you?

We currently have customer who do something similar based on data they 
get from us. Specifically, they get an entity data stream, and use 
semantically marked-up world geometry to do automated analysis of 
performance. One specific application is where their system will check 
whether soldiers traversing a street is exposing themselves too much to 
possible attack -- the output is qualitative information like "you put 
teammates 2 and 3 in the cone of fire from this doorway for too long at 
time 13:03 into the exercise" or "your team stacked against this 
structurally unsound wall at time 8:30 and stayed there for four minutes."

That external application (not built or controlled by us) receives a 
text representation of entity data, and process that directly. It is not 
currently LLSD XML serialized data (for mostly obvious reasons :-), but 
if "MMSD" was capable of serving this use case in a useful (and not too 
chatty) way, then I would be all for it -- suitable standards are a good 
thing, and our customer would then also be able to tie their application 
into any virtual world that provides the same kind of data stream.