[sldev] Google data exchange format

John Hurliman jhurliman at jhurliman.org
Wed Jul 9 19:57:18 PDT 2008

I'm not sure LLSD-GDE (protobuf) carries any meaning. LLSD (in the abstract
sense, not one of the three serializations) defines how objects (and arrays
and key value pairs and so on) are set/accessed in code, and protobuf
generates a series of classes that define how you set/access objects in
code. libprotobuf also provides methods to hook in new
serialization/deserialization methods. LLSD, LL's message template system,
and protobuf all do the exact same thing in slightly different ways. You can
implement message_template in protobuf or make an LLSD-Binary serializer for
protobuf for fun and profiling/comparison (the SL protocol already
implements message_template in LLSD-XML to complete the circle), but I don't
think it would make sense to use a mashup of two or three of the systems as
a standard.


On Wed, Jul 9, 2008 at 6:32 PM, Lawson English <lenglish5 at cox.net> wrote:

> Lawson English wrote:
>> Seems to me that LLSD would be a single format file in this system. If it
>> is robust enough, could replace the LLSD XML format without any code changes
>> save the one function. Would allow for gradual switchover since a new viewer
>>  could request  caps to use the new format, while the default would be the
>> current format.
> Also, seems to me that pyogp would be a great test for comparing throughput
> using LLSD-XML vs LLSD-GDE.
> Lawson
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/SLDev
> Please read the policies before posting to keep unmoderated posting
> privileges
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20080709/d1951885/attachment-0001.htm

More information about the SLDev mailing list