OpenSim Services and Service Connectors - Revision history

Manni at 18:33, 21 February 2023

2023-02-21T18:33:53Z

Justincc at 20:50, 24 September 2012

2012-09-24T20:50:09Z

MakoBot: Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

2012-03-04T06:50:51Z

Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

MakoBot: Robot: Cosmetic changes

2012-03-04T03:46:41Z

Robot: Cosmetic changes

Justincc at 00:08, 5 July 2011

2011-07-05T00:08:33Z

Makopoppo at 09:12, 4 June 2011

2011-06-04T09:12:24Z

Newacct at 00:43, 17 April 2010

2010-04-17T00:43:33Z

Diva at 03:15, 19 September 2009

2009-09-19T03:15:01Z

Diva at 15:12, 22 May 2009

2009-05-22T15:12:36Z

Diva at 15:12, 22 May 2009

2009-05-22T15:12:15Z

← Older revision		Revision as of 18:33, 21 February 2023
Line 1:		Line 1:
−	{{Quicklinks}}	+	{{Quicklinks\|OpenSim Services and Service Connectors}}

	{{Warning\|This documentation, though still useful, is rather out of date.		{{Warning\|This documentation, though still useful, is rather out of date.

@@ Line 1: / Line 1: @@
 {{Quicklinks}}
-{{Warning|This documentation, though still useful, is rather out of date.  Please see [[Connectors]] for more accurate information}}
+{{Warning|This documentation, though still useful, is rather out of date.
 = Introduction to OpenSimulator Services and Service Connectors =

@@ Line 4: / Line 4: @@
 {{Warning|This documentation, though still useful, is rather out of date.  Please see [[Connectors]] for more accurate information}}
-= Introduction to OpenSim Services and Service Connectors =
+= Introduction to OpenSimulator Services and Service Connectors =
-The OpenSim framework is becoming so many things to so many people that it has reached the point where the original architecture of the software itself, largely inspired by what the SL Client dictates and by the Linden Lab grid, is hampering progress on all those fronts. We need to rethink the architecture of the software in order to be able to support the variety of things that people want to do with OpenSim without having to go through lengthy design discussions and negotiations for it to do "the right thing", which obviously doesn't exist. For some, "the right thing" is a server infrastructure that is a 100% reproduction of Second Life; for others, "the right thing" is a 3D server infrastructure that is 100% compatible with the Web; for others, "the right thing" is a desktop 3D simulator; and for many others "the right thing" is many points in between.
+The OpenSimulator framework is becoming so many things to so many people that it has reached the point where the original architecture of the software itself, largely inspired by what the SL Client dictates and by the Linden Lab grid, is hampering progress on all those fronts. We need to rethink the architecture of the software in order to be able to support the variety of things that people want to do with OpenSimulator without having to go through lengthy design discussions and negotiations for it to do "the right thing", which obviously doesn't exist. For some, "the right thing" is a server infrastructure that is a 100% reproduction of Second Life; for others, "the right thing" is a 3D server infrastructure that is 100% compatible with the Web; for others, "the right thing" is a desktop 3D simulator; and for many others "the right thing" is many points in between.
 This proposal comes in the sequence of an email thread on the -dev mailing list:
@@ Line 35: / Line 35: @@
 * We move away from the current boolean architectural choices given by the variable "gridmode=true|false", and into a model where simulators can be configured in a variety of hybrid modes.
 * The dynamic loading of service connectors into the simulator allows a variety of protocols "on-the-wire" between the simulator and the services without having to change the simulator code. (As long as that service implementation can honor the established service interface for it)
-* [Corollary of the previous] All discussions about simulator-service protocols (HTTP vs XMLRPC vs ...) become irrelevant to the OpenSim framework itself. Opensim will continue to provide a few service implementations and their connectors out-of-the-box, but anyone can replace those with their own without having to make any changes to the source code of the Simulator, by making the corresponding connector DLL available to the simulators.
+* [Corollary of the previous] All discussions about simulator-service protocols (HTTP vs XMLRPC vs ...) become irrelevant to the OpenSimulator framework itself. Opensim will continue to provide a few service implementations and their connectors out-of-the-box, but anyone can replace those with their own without having to make any changes to the source code of the Simulator, by making the corresponding connector DLL available to the simulators.
-* All OpenSim servers become server shells of the same type. That is, they are all configured through the .ini mechanism, and they can run any of the services and service connectors. Therefore, it also becomes trivially possible to have system architectures where some resource service uses another resource service directly. For example, the Inventory server may use the Asset server in order to provide a combined IInventoryService+IAssetService interface to viewers.
+* All OpenSimulator servers become server shells of the same type. That is, they are all configured through the .ini mechanism, and they can run any of the services and service connectors. Therefore, it also becomes trivially possible to have system architectures where some resource service uses another resource service directly. For example, the Inventory server may use the Asset server in order to provide a combined IInventoryService+IAssetService interface to viewers.
 == Implementation of the Proposed Software Architecture ==
@@ Line 114: / Line 114: @@
 === Service Interfaces ===
-'''OpenSim.Services.Interfaces''': This DLL contains all the service interfaces known to OpenSim.
+'''OpenSim.Services.Interfaces''': This DLL contains all the service interfaces known to OpenSimulator.
 Here is how IAssetService looks like:
@@ Line 316: / Line 316: @@
 === Service Implementations ===
-'''OpenSim.Services.AssetService''': the default OpenSim implementation of the asset service. Here is a snippet:
+'''OpenSim.Services.AssetService''': the default OpenSimulator implementation of the asset service. Here is a snippet:
 <source lang="csharp">

@@ Line 4: / Line 4: @@
 {{Warning|This documentation, though still useful, is rather out of date.  Please see [[Connectors]] for more accurate information}}
-=Introduction to OpenSim Services and Service Connectors=
+= Introduction to OpenSim Services and Service Connectors =
 The OpenSim framework is becoming so many things to so many people that it has reached the point where the original architecture of the software itself, largely inspired by what the SL Client dictates and by the Linden Lab grid, is hampering progress on all those fronts. We need to rethink the architecture of the software in order to be able to support the variety of things that people want to do with OpenSim without having to go through lengthy design discussions and negotiations for it to do "the right thing", which obviously doesn't exist. For some, "the right thing" is a server infrastructure that is a 100% reproduction of Second Life; for others, "the right thing" is a 3D server infrastructure that is 100% compatible with the Web; for others, "the right thing" is a desktop 3D simulator; and for many others "the right thing" is many points in between.
@@ Line 463: / Line 463: @@
 * [[OpenSim:Introduction_and_Definitions#UGAIM_Services|What are UGAIM Services?]]
-* [[OpenSim_Services_and_Service_Connectors | Services and Service Connectors Main Page]]
+* [[OpenSim Services and Service Connectors|Services and Service Connectors Main Page]]
-* [[Services and Service Connectors Configuration |Services and Service Connectors Configuration Page]]
+* [[Services and Service Connectors Configuration|Services and Service Connectors Configuration Page]]
 = Change Log =
@@ Line 472: / Line 472: @@
 [[Category:Users]]
 [[Category:Support]]
 [[Category:Tech Reference]]
 [[Category:Help]]
 [[Category:Configuration]]
-[[Category:Getting_Started]]
+[[Category:Getting Started]]
 [[Category:Development]]

@@ Line 1: / Line 1: @@
 __NOTOC__
 {{Quicklinks}}
 =Introduction to OpenSim Services and Service Connectors=

@@ Line 300: / Line 300: @@
                  throw new Exception("No AssetService in config file");
-             Object[] args = new Object[] { config };
+             Object[] args = { config };
              m_AssetService =
                      ServerUtils.LoadPlugin<IAssetService>(assetService, args);
@@ Line 404: / Line 404: @@
                  m_log.InfoFormat("[SERVER]: Loading {0}", friendlyName);
-                 Object[] modargs = new Object[] { m_Server.Config, m_Server.HttpServer };
+                 Object[] modargs = { m_Server.Config, m_Server.HttpServer };
                  IServiceConnector connector =
                          ServerUtils.LoadPlugin<IServiceConnector>(conn,

@@ Line 2: / Line 2: @@
 {{Template:Quicklinks}}
 <br />
 == [[Technical Reference | Technical Reference]] ==

← Older revision		Revision as of 15:12, 22 May 2009
Line 16:		Line 16:

	Proposers: Diva and Melanie		Proposers: Diva and Melanie
		+
	Closing date: 5/28/09		Closing date: 5/28/09

@@ Line 14: / Line 14: @@
 https://lists.berlios.de/pipermail/opensim-dev/2009-April/006325.html
 The general ideas here are similar to those already in place for using Database and Physics engines. This proposal is about extending those general ideas to all Resource Services, which carries the additional difficulty of having to deal with service placement and service composition.
 == Proposal Summary ==
@@ Line 466: / Line 469: @@
 * [[Technical_Reference|Technical Reference Page]]
 * [[Status|Main Status Page]]
 [[Category:Users]]