It might be good to separate out generic capabilities code from Linden specifics in case some other environment uses them in the future. However, this is speculative.

Also, perhaps a typo point is the the current module is OpenSim.Region.ClientStack.LindenUDP, rather than OpenSim.Region.ClientStackLindenUDP

On 29/04/11 22:19, Diva Canto wrote:
I would like to clean up the way OpenSim handles capabilities. Here are my 
goals:
(1) move everything-capabilities into LL space, because this is something 
that's very specific to the Linden-family of
clients; and
(2) make Capability URLs be externally configurable so that some of those 
services can be served from a Robust server,
if operators see that need

More specifically, I would like to:

- rename OpenSim.Region.ClientStackLindenUDP to OpenSim.Region.ClientStackLinden
- create two folders in there: UDP and Capabilities
- Move everything that's currently under OpenSim.Region.ClientStackLindenUDP to 
the subfolder UDP
- Move OpenSim.Framework.Capabilities to the subfolder Capabilities
- Move the module that's currently in 
OpenSim.Region.CoreModules.Agent.Capabilities (CapabilitiesModule) to
OpenSim.Region.ClientStackLinden.Capabilities
- Move what's currently in OpenSim.Region.CoreModules.Framework.EventQueue to 
OpenSim.Region.ClientStackLinden.Capabilities
- Move what's currently in OpenSim.Region.CoreModules.Framework.Avatar.Assets to
OpenSim.Region.ClientStackLinden.Capabilities
- refactor some of these modules, so that the handlers themselves are in 
OpenSim.Server.Handlers, so that they can be
served from a Robust server

Thoughts? Objections? Cautions?

Crista / Diva


_______________________________________________
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev



--
Justin Clark-Casey (justincc)
http://justincc.org/blog
http://twitter.com/justincc
_______________________________________________
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev

Reply via email to