Open Standards & Plugins (was: Re: [sldev] Why Linden Labs needs to )

[Dzonatas]

One thing people forget about is open standards besides just open 
source. I actually recommended that LL publish open standards of the 
protocol between the client and the server. The open standards basically 
give you the plug-in API that everyone has wanted.

LL has published the open source client. I believe that goes beyond the 
open standards; however, it does not settle on any specific open 
standard also, but it documents the possibilities openly. This is what 
people miss the point on.

Put down the flamethrowers and corporate backers over the plug-in API 
and lets get down to business with the open standard.

Why haven't the message templates of the network protocol been 
documented on the wiki as of yet?

Aren't you "plugging-in" to the server?

Thank you!

Tim Shephard wrote:
> Since this thread has become high volume in such a short period of
> time, I've created a wiki page here:
>
> https://wiki.secondlife.com/w/index.php?title=Plugin_closed_source&action=edit 
>
>
> thx,
>
> Tim.
>
> On 4/6/07, Ettore Pasquini <ettore_pasquini at 3dconnexion.com> wrote:
>>
>>
>> >>> So: open up that plugin API.    Talk clearly and consistently about
>> >>> how we can extend the client and maintain our own closed source.
>>
>> Hmm, closed source plugins for an open source app... Doesn't that sound
>> weird, at best? If you really want it to be approved by LL and the
>> community, you really need to explain what advantages a closed source 
>> plugin
>> architecture would bring over an open source one. And write it of 
>> course.
>>