Home

 

Download

 

News

 

Support

 

Admin

 

Dev

 

Screen Shots

 

Grid List

 

Bugs

Languages:

English    Deutsch    Français

Introduction

OpenSimulator is a large and organically grown project, so its architecture is still subject to change. As such, there are very few formal internal interfaces - region modules operating by plugging in directly to the core internals.

Architecture

Packages

• OpenSim. This contains the classes which launch the OpenSimulator region server and handle the console
  • Startup
    • The Main() for OpenSim.exe can be found in the file OpenSim/Region/Application/Application.cs. It does a bunch of configuration checks, but the meat of it is the instantiation of an OpenSim object, calling its Startup() method (which gets things rolling in separate threads), and then blocking the initial thread by prompting on the main console (using the Prompt() method MainConsole.Instance)
    • OpenSim.OpenSim.Startup() comes from an ancestor, OpenSim.Framework.Servers.BaseOpenSimServer; it calls StartupSpecific()

• OpenSim.Addons. OpenSimulator components which came originally from the Diva distribution. Hence their different organization compared to other features.
  • OpenSim.Addons.Groups. Core support for user groups.
  • OpenSim.Addons.OfflineIM. Core support for offline IM.
• OpenSim.ApplicationPlugins. Each package is an individual application plugin - an application plugin is a modular piece of code that has an effect on the entire region server. See RegionModules for more details or one of justincc's blogposts for a higher level overview (which should really be in this wiki).
• OpenSim.Capabilities. Basic structures for capabilities support.
• OpenSim.ConsoleClient. RestConsole for connecting remotely to the OpenSimulator console. Not widely used as of yet - more commonly OpenSimulator is started in a screen instance in Linux and in separate terminals in Windows.
• OpenSim.Data. This is all the low level database manipulation stuff. In here, you'll see packages for SQLite, MySQL and MSSQL (which tends to lag).
• OpenSim.Framework. General framework code used by the rest of OpenSimulator which is either not specific to regions or used in common with regions and other classes.
  • OpenSim.Framework.AssetLoader.Filesystem. Small DLL used to load library assets from the filesystem.
  • OpenSim.Framework.Communications. Some comms related odds and ends. Notably request limiting code in OpenSimulator master git branch post 0.7.6.
  • OpenSim.Framework.Configuration.HTTP. Old code for loading configuration via HTTP. May have decayed beyond usefulness.
  • OpenSim.Framework.Configuration.XML. Code for loading XML config files (as opposed to INI). May have decayed beyond usefulness.
  • OpenSim.Framework.Console. Framework classes for the OpenSimulator console.
  • OpenSim.Framework.Monitoring. Statistics gathering and monitoring infrastructure.
  • OpenSim.Framework.RegionLoader.FileSystem. Code for loading region configuration from the filesystem (e.g. bin/Regions/Regions.ini).
  • OpenSim.Framework.RegionLoader.Web. Code for loading region configuration remotely.
  • OpenSim.Framework.Serialization. Infrastructure for OAR and IAR read and write.
  • OpenSim.Framework.Servers. Contains generic server code, such as the base OpenSimulator server and http servers.
• OpenSim.Region. Contains most of the meaty code that it specifically concerned with regions/scenes.
  • OpenSim.Region.ClientStack. Small amount of infrastructure for making different UDP client stacks available (though currently only LLUDP exists).
  • OpenSim.Region.ClientStack.LindenCaps. The code necessary for communicating with clients using the HTTP (capability) part of the Second Life protocol. Glues data going to/from the client to region modules that handle specific aspects.
  • OpenSim.Region.ClientStack.LindenUDP. The code necessary for communicating with clients using the UDP part of the Second Life protocol. Glues data going to/from the client to scene and region module code.
  • OpenSim.Region.CoreModules. The region modules considered core to OpenSimulator (and thus come bundled with it). This covers a vast range. For example, the Avatar/Attachments/AttachmentsModule handles avatar attachments (though with many structures still in core region code). The Framework/EntityTransfer/EntityTransferModule handles region crossings and teleports (though again in co-operation with large chunks of core region code).
  • OpenSim.Region.DataSnapshot. Code for creating an XML file that summarises the contents of the region. Could be exposed to an external search engine.
  • OpenSim.Region.Framework. The framework for the region itself, including scene graph, scene presence (agent) classes, scene object classes, inventory, etc. Could be considered the core of the simulator.
  • OpenSim.Region.OptionalModules. Optional region modules that aren't considered core to the simulator. In principle, could be removed yet have a working Second Life compatible simulator, though this has not been well tested.
  • OpenSim.Region.Physics. General physics framework code and plugins for specific engines (BulletSim, ODE, etc). Only the ODE and BulletSim modules are mature or complete enough for use.
  • OpenSim.Region.RegionCombinerModule. Module for megaregion support.
  • OpenSim.Region.ScriptEngine. Script engine code that powers the scripts run within OpenSimulator. Currently there is only one engine bundled with OpenSimulator, XEngine.
  • OpenSim.Region.UserStatistics. Web Statistics Module for exposing some simulator information via a webpage.
• OpenSim.Server. Server infrastructure.
  • OpenSim.Server.Base. Common server infrastructure for the simulator and Robust grid servers.
  • OpenSim.Server.Handlers. Classes for handling raw incoming data and translating these to service requests. Used mainly in grid mode for ROBUST server instances. For instance, Asset/AssetServerGetHandler translates internal asset fetch requests to the asset service and replies with the results.
• OpenSim.Services. Code which provides both service implementations (e.g. AssetService to read and write assets to persistent storage) interfaces and infrastructure (chiefly OpenSim.Services.Connectors which creates the actually HTTP requests to invoke services remotely). In grid mode, these are instantiated within Robust.exe instances. In standalone mode, these are instantiated directly in OpenSim.exe.
• OpenSim.Tests.*. Test code, both common infrastructure used in regression tests and some standalone client test code. Actual regression tests are spread throughout the code base in separate *.Test packages (e.g. OpenSim.Region.Framework.Tests project).
• OpenSim.Tools. Some OpenSimulator associated tools. Not used in actual OpenSimulator operation.
• pCampbot. A test tool which uses bots to simulate activity load on a simulator. See pCampbot for more details. Not used in actual OpenSimulator operation.

Coding restrictions

Because OpenSimulator has to run on both Windows and Mono (usually on Linux or Mac), we are limited to the parts of .net that the minimum version of Mono we require supports.