[sldev] framework documentation pattern

[John Hurliman]

Ryan Williams (Which) wrote:
> Lawson English wrote:
>   
>> The LLSD class seems to be designed to allow better communication
>> between framework objects, among other uses, so any redesigned classes
>> should probably use LLSD when talking to each other. This last is only
>> the vaguest of intuitions on my part, so feel free to gently correct
>> me if I'm wrong about its intended use or the utility of using it when
>> rewriting the framework.
>>     
> Sounds right to me.  :-)  Though of course LLSD is not the hammer for
> every nail.
>   

I'm not sure that sounds right at all. Serializing and deserializing 
data to blobs of LLSD/XML/whatever when making calls from class to class 
is not going to make things more interoperable then just passing 
arguments, you are just spending a lot of CPU cycles (an incredible 
amount considering it would be done on ever cross-class call) to mangle 
and unmangle data. And compatibility will still break and need to be 
documented when something changes, LLSD doesn't address that problem at all.

LLSD allows widely different programs and languages (for example a C++ 
client and a python web server) to have a common language to interact 
with. A C++ class calling a C++ class already has that common language.

John Hurliman