Technical Reference/terms
From OpenSimulator
m |
m (Robot: Cosmetic changes) |
||
| Line 7: | Line 7: | ||
=== What do all these terms mean? === | === What do all these terms mean? === | ||
| − | [[Definitions | Technical Reference Terms and Definitions]] | + | [[Definitions|Technical Reference Terms and Definitions]] |
| Line 14: | Line 14: | ||
Definition of some common terms: | Definition of some common terms: | ||
| − | '''Region'''<br/> | + | '''Region'''<br /> |
A region has an (x/y) position in a grid, and a region-handle calculated from the position. A region can also be defined as an IP Endpoint that the Viewer can establish a client connection to. The unique id of a region is a uuid, this means that a region can change position, and because of that position change, it the handle will be recalculated. The handle will uniquely identify a position in a grid. | A region has an (x/y) position in a grid, and a region-handle calculated from the position. A region can also be defined as an IP Endpoint that the Viewer can establish a client connection to. The unique id of a region is a uuid, this means that a region can change position, and because of that position change, it the handle will be recalculated. The handle will uniquely identify a position in a grid. | ||
| Line 21: | Line 21: | ||
* Client/Viewer circuits | * Client/Viewer circuits | ||
| − | '''Scene'''<br/> | + | '''Scene'''<br /> |
A scene is part of a region, currently there is a one to one relationship, i.e. one region has one scene. A scene contains all the 3d ''objects'', called ''Entities'', entities can either be ScenePresences or SceneObjectGroups. A ScenePresence can be represented by an avatar, if it is a root scene presence. SceneObjectGroups consists of a number of SceneObjectParts. | A scene is part of a region, currently there is a one to one relationship, i.e. one region has one scene. A scene contains all the 3d ''objects'', called ''Entities'', entities can either be ScenePresences or SceneObjectGroups. A ScenePresence can be represented by an avatar, if it is a root scene presence. SceneObjectGroups consists of a number of SceneObjectParts. | ||
| − | '''Avatar/ScenePresence'''<br/> | + | '''Avatar/ScenePresence'''<br /> |
Each viewer is represented by one or more avatars. The Root avatar or ScenePresense functions as a kind of cursor, into the grid. Where the region will keep the viewer updated on the state of the simulation, taking place in the scene. Besides the root presence, a number of child presences will exist in the neighboring regions, enabling the viewer to know what is going on in the neighboring regions. | Each viewer is represented by one or more avatars. The Root avatar or ScenePresense functions as a kind of cursor, into the grid. Where the region will keep the viewer updated on the state of the simulation, taking place in the scene. Besides the root presence, a number of child presences will exist in the neighboring regions, enabling the viewer to know what is going on in the neighboring regions. | ||
| − | '''Viewer'''<br/> | + | '''Viewer'''<br /> |
An application which is used to view the state of the simulation. Currently only three different viewers are known: the LL viewer, the OpenSL test client and AjaxLife. | An application which is used to view the state of the simulation. Currently only three different viewers are known: the LL viewer, the OpenSL test client and AjaxLife. | ||
| − | '''Session'''<br/> | + | '''Session'''<br /> |
Each connection between a viewer and a region, regardless if the avatar is the root or a child, is a session. | Each connection between a viewer and a region, regardless if the avatar is the root or a child, is a session. | ||
| − | '''Simulator'''<br/> | + | '''Simulator'''<br /> |
A program which can manage several ''Regions'' | A program which can manage several ''Regions'' | ||
---- | ---- | ||
| − | * [[ | + | * [[OpenSim.cs]] (OpenSim.cs ) |
| − | * [[ | + | * [[OpenSim SwInit|OpenSim_SwInit]] (Initialization from Main() ) |
| − | * [[ | + | * [[OpenSim SwMainLoopl|OpenSim_SwMainLoopl]] (After initialization, a main loop waits for connections or commands) |
| − | * [[ | + | * [[OpenSim SwRegionHandshake|OpenSim_SwRegionHandshake]] (How a client connects to the simulator) |
| − | * [[ | + | * [[OpenSim UserService|OpenSim_UserService]] (How the user server works) |
| − | * [[ | + | * [[OpenSim InterRegionCommunications|OpenSim_InterRegionCommunications]] (How the sim communicates with other sims) |
| − | * [[ | + | * [[OpenSim GridService|OpenSim_GridService]] (How the grid server works) |
| − | * [[ | + | * [[OpenSim AssetService|OpenSim_AssetService]] (How the asset server works) |
| − | * [[ | + | * [[OpenSim SimService|OpenSim_SimService]] (How the simulator operates after a connection is made) |
| − | * [[ | + | * [[Sim Throttles|Sim_Throttles]] (How the simulator handles throttling of packets) |
| − | <br> | + | <br /> |
= See Also = | = See Also = | ||
* [[:Category:Support| Support pages]] | * [[:Category:Support| Support pages]] | ||
* [[:Category:Getting_Started|Getting Started]] | * [[:Category:Getting_Started|Getting Started]] | ||
| − | * [[ | + | * [[OpenSim Archives|How to use OpenSim Archives (OAR)]] |
[[Category:Users]] | [[Category:Users]] | ||
| Line 58: | Line 58: | ||
[[Category:Help]] | [[Category:Help]] | ||
[[Category:Configuration]] | [[Category:Configuration]] | ||
| − | [[Category: | + | [[Category:Getting Started]] |
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 20:15, 3 March 2012
 |
Languages: |
|
|
|
This article or section contains incomplete information. Please help us by completing the content on this page. |
This is a set of software technical reference pages that include definitions and describe how the simulator works from invocation, initialization, main loop and various services.
What do all these terms mean?
Technical Reference Terms and Definitions
Definition of some common terms:
Region
A region has an (x/y) position in a grid, and a region-handle calculated from the position. A region can also be defined as an IP Endpoint that the Viewer can establish a client connection to. The unique id of a region is a uuid, this means that a region can change position, and because of that position change, it the handle will be recalculated. The handle will uniquely identify a position in a grid.
A region contains a number of sub components:
- Scene
- Client/Viewer circuits
Scene
A scene is part of a region, currently there is a one to one relationship, i.e. one region has one scene. A scene contains all the 3d objects, called Entities, entities can either be ScenePresences or SceneObjectGroups. A ScenePresence can be represented by an avatar, if it is a root scene presence. SceneObjectGroups consists of a number of SceneObjectParts.
Avatar/ScenePresence
Each viewer is represented by one or more avatars. The Root avatar or ScenePresense functions as a kind of cursor, into the grid. Where the region will keep the viewer updated on the state of the simulation, taking place in the scene. Besides the root presence, a number of child presences will exist in the neighboring regions, enabling the viewer to know what is going on in the neighboring regions.
Viewer
An application which is used to view the state of the simulation. Currently only three different viewers are known: the LL viewer, the OpenSL test client and AjaxLife.
Session
Each connection between a viewer and a region, regardless if the avatar is the root or a child, is a session.
Simulator
A program which can manage several Regions
- OpenSim.cs (OpenSim.cs )
- OpenSim_SwInit (Initialization from Main() )
- OpenSim_SwMainLoopl (After initialization, a main loop waits for connections or commands)
- OpenSim_SwRegionHandshake (How a client connects to the simulator)
- OpenSim_UserService (How the user server works)
- OpenSim_InterRegionCommunications (How the sim communicates with other sims)
- OpenSim_GridService (How the grid server works)
- OpenSim_AssetService (How the asset server works)
- OpenSim_SimService (How the simulator operates after a connection is made)
- Sim_Throttles (How the simulator handles throttling of packets)
