0.7 Planning
From OpenSimulator
| Line 7: | Line 7: | ||
* FreeSwitch -- voice | * FreeSwitch -- voice | ||
* Friends -- social net | * Friends -- social net | ||
| + | * Gatekeeper -- hypergrid foreign users control | ||
* Grid -- maps map locations to IPs and regions | * Grid -- maps map locations to IPs and regions | ||
* Grid User -- grid-local information about users | * Grid User -- grid-local information about users | ||
| Line 14: | Line 15: | ||
* Profile (Basic) -- user profiles | * Profile (Basic) -- user profiles | ||
* User Accounts -- administrative info about users | * User Accounts -- administrative info about users | ||
| + | * User Agents -- hypergrid local users protection | ||
The simulators access these services through abstract interfaces, therefore being isolated from implementation details. The services can now be seamlessly instantiated in any process, namely ROBUST server shells and the simulators processes themselves, which means that we have complete reuse of code between standalone and grid configurations. The specification is done in configuration files (.ini). Moreover, access to remote services is also seamlessly achieved through the instantiation of stubs (aka service connectors); again, the specification of which stubs the simulators use is done externally in configuration files (.ini) -- this allows for alternative third-party implementations of the resource service infrastructure, of which there is already one (SimianGrid). | The simulators access these services through abstract interfaces, therefore being isolated from implementation details. The services can now be seamlessly instantiated in any process, namely ROBUST server shells and the simulators processes themselves, which means that we have complete reuse of code between standalone and grid configurations. The specification is done in configuration files (.ini). Moreover, access to remote services is also seamlessly achieved through the instantiation of stubs (aka service connectors); again, the specification of which stubs the simulators use is done externally in configuration files (.ini) -- this allows for alternative third-party implementations of the resource service infrastructure, of which there is already one (SimianGrid). | ||
| Line 34: | Line 36: | ||
* #2549: Avatars always login into T pose | * #2549: Avatars always login into T pose | ||
* #4613: IAR load/save | * #4613: IAR load/save | ||
| + | |||
| + | == MUST DO documentation == | ||
| + | |||
| + | * Improve [[ROBUST]] | ||
Revision as of 19:30, 25 March 2010
Release 0.7 will be the first one featuring the completed major refactoring and rearchitecting work that happened during the second half of 2009 and the first quarter of 2010. This work targeted mainly the resource services and servers previously known as UGAIM. These servers have been replaced by one single server shell called ROBUST which can now run any combination of services in it. The services themselves have been reconceptualized; we now have the following set of main services:
- Assets -- the asset store
- Authentication -- passwords and auth tokens
- Authorization -- access control
- Avatar -- the visual representation of users, formerly known as "avatar appearance"
- FreeSwitch -- voice
- Friends -- social net
- Gatekeeper -- hypergrid foreign users control
- Grid -- maps map locations to IPs and regions
- Grid User -- grid-local information about users
- Inventory -- the inventory store
- Login -- the login service
- Presence -- tracks where in the grid user agents are
- Profile (Basic) -- user profiles
- User Accounts -- administrative info about users
- User Agents -- hypergrid local users protection
The simulators access these services through abstract interfaces, therefore being isolated from implementation details. The services can now be seamlessly instantiated in any process, namely ROBUST server shells and the simulators processes themselves, which means that we have complete reuse of code between standalone and grid configurations. The specification is done in configuration files (.ini). Moreover, access to remote services is also seamlessly achieved through the instantiation of stubs (aka service connectors); again, the specification of which stubs the simulators use is done externally in configuration files (.ini) -- this allows for alternative third-party implementations of the resource service infrastructure, of which there is already one (SimianGrid).
This page is the main planning document for the 0.7 release.
MUST DO features
- GridUser service in place, replacing the home info storage that is currently done awkwardly by the presence service
- Estate owner feature restored, as a replacement of Master Avatar
MUST FIX bugs
- Assorted DB migration issues fleshed out and fixed (several mantis)
- #4603 Remote Admin bugs
- #4622
- #3522: After login sometimes the avatar is in over 10 kilometers height and looks to the stars
- #4405: Even if object was attached to avatar, the attachment of the object comes off by next login.
- #4561: Set Home makes the users table show random values
- #2549: Avatars always login into T pose
- #4613: IAR load/save
MUST DO documentation
- Improve ROBUST
