Re: [mmox] XML serialization

[Jon Watte <[e-mail]>]

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.

Sincerely,

jw