[sldev] RE: Speed of adopting open practices (Re: IJIRA and PJIRA)

Christian Scholz / Tao Takashi (SL) tao.takashi at googlemail.com
Mon Jul 14 06:29:27 PDT 2008


Hi!

On Sun, Jul 13, 2008 at 4:22 AM, Edward Artaud <edward.artaud at gmail.com> wrote:
>
> On Sat, Jul 12, 2008 at 4:53 PM, Lawson English <lenglish5 at cox.net> wrote:
>>
>> Seriously, its a set of protocols (very limited at the moment) to
>> facilitate grid interop, and it eventually will become the basis for a [more
>> or less] complete redesign of the server architecture (I suspect) and  even
>> further off, the client (I hope).
>
>
> That was my concern when I was posting about the need for a plug-in
> architecture.  Is it likely that OGP will yield anything useful for the
> client until this time next year?  Most of the actual coding will go into
> PyOGP, so by the end of the year, it'll be roughly equivalent in terms of
> functionality to where libsl (openmv) is today, but using the cleaner
> protocol and in Python rather than C#.  At that point, I suppose it'll need
> to be ported to C++ and somehow bolted onto the SL viewer, which will take
> another 6 months, and then we'll be roughly where we are today, but with a
> new underlying protocol layer.  At that point, we'll be able to start
> refactoring the viewer architecture.  I hope I'm wrong and it takes half
> that time.

I don't think the path will be protocol => Python => C++, it is more
likely that it's a parallel thing between Python and C++. Linden Lab
already implemented the login part into a branch of their existing
viewer.

But as Q laid out, it simply takes it's time to build a quality
protocol esp. as it's not the simplest one and additionaly has many
social issues, too.

What it enables on the long run though is I think also many
implementations of the client. Right now I wouldn't dare to start a
new one because
a) the existing protocol is not really documented
b) it might change quite often in maybe not documented ways

With an official definition which maybe even has gone through a
standardization institution it cannot change that often. It can also
not change that often given the numbers of servers and different grid
running it then. So you are on a safer side to write such a client.
And a client can then be of any complexity you like, be it just text,
2D or 3D with more or less features. I think even a browser plugin
might then be easier.

-- Tao


-- 
Christian Scholz
Tao Takashi (Second Life name)
taotakashi at gmail.com
Blog/Podcast: http://mrtopf.de/blog
Planet: http://worldofsl.com

Company: http://comlounge.net
Tech Video Blog: http://comlounge.tv
IRC: MrTopf/Tao_T


More information about the SLDev mailing list