OpenSimulator:0.5 Release Target Discussion
From OpenSimulator
(Difference between revisions)
Line 13: | Line 13: | ||
<br/> | <br/> | ||
− | == As part of the new protocol, | + | == As part of the new protocol, overhaul the "commsmanager"== |
*A lot of the functions currently in there, needs moving out. Like most of the Caps handling needs to be moved to the backend servers (possible with a dedicated Caps Manager server, like LL seem to have). | *A lot of the functions currently in there, needs moving out. Like most of the Caps handling needs to be moved to the backend servers (possible with a dedicated Caps Manager server, like LL seem to have). |
Revision as of 22:14, 6 September 2007
Suggested Goals
ODE/ Physics
- I respectfully and self-servedly recommend ODE support as a core feature of 0.5.
- Even though there are still legitimate questions about ODE's stability, it works well enough already to get ppl excited. Most of the work for the core team will transport to any other physics plugin, ie bullet or physx.
- If there is still a strong desire to completely redesign the physics interface, let's bite the bullet and do it. A world without physics is like -- well, a world without photons!
New Backend Protocol (OGS 2)
As part of the new protocol, overhaul the "commsmanager"
- A lot of the functions currently in there, needs moving out. Like most of the Caps handling needs to be moved to the backend servers (possible with a dedicated Caps Manager server, like LL seem to have).
- Inventory handling should move to a module. As should Xfer uploads.
Rewrite Asset Cache/Server
Improve the management of client updates
- Use a "interest list" for each connected client, so they only get updated about prims/objects that are in range (or they need to know about).
- Combine objects (parts) into single packets, rather than sending a separate packet for each prim as currently happens.
Finish implementing the ll functions for scripting.
Improve UDP network code (ClientStack)
Clean up the IClientAPI interface
Start to think more about security ? (most likely will not happen until a later version)
- Add security sinks in the "region to region" .Net remoting process.
- Check for security wholes in scripting engine.
Tighter integration of DataStore into the core