[Opensim-dev] users and agents table, and other oddities?

[Stefan Andersson]

> Let me try to come up with a few definitions of terms, which doesn't require > a lot of refactoring:
Add them to the wiki for further elaboration and discussion
 > Sim/Simulator: a program which runs a simulation of objects interacting, > possibly with the involvement of simulated physics.> > Region: a 256x256 wide area, having a terrain and a number of objects, > interacting
A region has an (x/y) position in a grid, and a regionhandle.
A region can also be defined as an IP Endpoint that the Viewer can establish a client connection to.
I wouldn't emphasis the 256x256 too much, as this is something some of us are looking into tweaking.
> A Sim can house multiple regions, and each region can house multiple objects
Actually, it is the Scene that hosts objects, the Region is a communications layer koncept.
 
At the time, we've been keeping things simple by having one region <-> one scene but that is sure to change.
 > An object can either be a collection of prims or an avatar
I guess the term we're using is 'Entity' which is subclassed into ScenePresences and SceneObjectGroups (that has SceneObjectParts)
 
A ScenePresence can have an Avatar (if it's the root)
> User: This represents a person in the real world, somthing which has an > email, a username etc.> > Viewer: an application which is used to view the state of the simulation. > Currently I know of three, the LL viewer, the OpenSL test client and > AjaxLife> > Agent: in a way, this can be thought of as a cursor, indicating what > position inside the simulator, the viewer is observing from., typically a > viewer will have multiple agents, a primary, often backed by an avatar, and > multiple child agents, in the neighboring regions.
An agent has a x/y position within the region; a 'root agent' is in the current region, and the viewer has 'child agents' that listens for changes in neighbouring sims.
> Session: Each connection between a viewer and an agent, regardless if the > agent is the primary or one of the child agents. Personally I would prefer > that we named child agents as sub-agents, and the sessions between the > viewer and sub-agents as sub-sessions.
Wouldn't that be each (authenticated?) connection between an client and a region?
 
An unauthenticated connection is called a 'Circuit'.
 
What is a 'sub' that a 'child' is not?
 > Unless somebody strongly objects to this convetion, I will start using that > naming convention in my codewriting.> > > One thing that we have repeatedly said is that we need to rewrite all the > > backend servers (ie user server etc) as the current ones are the result of > > very early work, from before we really knew how a lot of things worked or > > would work. One of the goals of 0.5 is meant to be that rewrite of the > > servers and the protocol between them and the regions.> > won't that hurt the goal of "frequent releases" ?
Baby steps, not rewrites.
 
/Stefan
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20071014/101b35fb/attachment-0001.html>