> - For the new protocols, we will have a new client stack at the server > side. The current viewer will be using both the old stack > and the new stack at the same time. When we reach the point that we can > develop a totally new viewer, we will use only the new stack and > implement rest of the protocols then.
> All in all, I hope this mail draw a rough picture of the > transition from the > old viewer to the new architecture, protocol and viewer. I hate to bring this up, but it's important. Will all the viewer components remain 100% GPL in licensing? It seems to me that the Linden code is 'infecting' all of Rex to the point where a less restrictive license is going to be difficult or impossible to implement. If there were some way to encourage LL to relicense at least some of the core libraries as LGPL, people like me could work on other parts of the client code without fear of running into the license issue. Alternatively, if some parts (say a behavior server) were architected using a message-passing protocol (as opposed to static or dynamic linking), my understanding is that that is outside the scope of GPL. I bring this up because I intend to continue as a core OpenSim developer, in order to work on protocol changes. I simply can't do that if I so much as download and browse through Real Extend's viewer source, given the way things stand now. -danx0r --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "realXtend" group. To post to this group, send email to realxtend@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/realxtend?hl=en -~----------~----~----~----~------~----~------~--~---
