I'm finally getting around to adding the AgentUpdate packets after login
which should stop the ghosting effect (if it does I'll look at options
for enabling or disabling that effect), and I need to use some more of
the information returned during login. The login server uses XML-RPC for
the exchange, except that several of the fields which are of type
<string></string> contain data in a format that looks more like JSON
than XML-RPC. I'm not sure if it is actually JSON or something vaguely
similar, has anyone seen something like this before? I don't want to
write a new parser if it's a standardized format.
In one example login, the look_at parameter contains:
[r0.8244629999999999459,r0.56591599999999997461,r0]
And the home parameter:
{'region_handle':[r262912, r257536], 'position':[r116.865, r169.874,
r21.7029], 'look_at':[r117.875, r169.875, r21.7029]}
If this is JSON the first parameter is an array, and the second is an
object with three members, each holding an array. But I don't think the
single quotes around member names are used in JSON (not positive on
this) and the "r" prefix on all the numbers is new to me as well.
Any suggestions?
John Hurliman
_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
