RegionIntegration - Revision history

Justincc: /* Integration through region modules */

2013-05-13T20:51:43Z

‎Integration through region modules

Justincc: /* Integration through region modules */

2012-07-19T23:43:04Z

‎Integration through region modules

Justincc: /* Techniques */

2012-07-19T23:41:54Z

‎Techniques

Justincc: /* Introduction */

2012-07-19T23:31:14Z

‎Introduction

Justincc: /* Techniques */

2012-07-19T23:31:04Z

‎Techniques

Justincc: Created page with "= Introduction = * This page is a work-in-progress * Integrating OpenSimulator regions with external sources of data can be done in a number of ways. = Techniques = == Sh..."

2012-07-19T23:30:56Z

Created page with "= Introduction = *** This page is a work-in-progress *** Integrating OpenSimulator regions with external sources of data can be done in a number of ways. = Techniques = == Sh..."

New page

= Introduction =

*** This page is a work-in-progress ***

Integrating OpenSimulator regions with external sources of data can be done in a number of ways.

= Techniques =

== Shared media/media on a prim.

Media on a prim (MOAP), also called Shared Media by Linden Lab, allows you to display and interact with any webpage on the surface of an object with version 2 and later Linden Lab viewers and third party viewers such as Firestorm and Kokua. See [http://community.secondlife.com/t5/English-Knowledge-Base/Shared-Media/ta-p/700145 this page] for more details.

@@ Line 17: / Line 17: @@
 == Integration through region modules ==
-OpenSimulator provides a [[region module|IRegionModule]] mechanism by which C# code can directly affect the objects in a region and can interface with any external system.  Using internal OpenSimulator code from a module is currently something of a black art, though the core distribution itself contains a large number of region modules and test code which can give examples of how to do this.  Also, as OpenSimulator is alpha code one has to expect that internal methods will change between releases with no warning.  This will remain the case until individual interfaces are formalized and/or OpenSimulator is considered in beta state.
+OpenSimulator provides a [[region module|IRegionModule]] mechanism by which C# code can directly affect the objects in a region and can interface with any external system.  Using internal OpenSimulator code from a module is currently something of a black art, though the core distribution itself contains a large number of region modules and test code which can give examples of how to do this.  Also, as OpenSimulator is alpha code one has to expect that internal methods will change between releases with no warning.  This will remain the case until individual interfaces are formalized.
 Region modules can also send and receive information from scripts via the [[OSSL_Script_Library/ModSendCommand]] mechanism.  In a future OpenSimulator release (0.7.4), region modules will also be able to make custom scripting functions available to scripts without having to manually patch and rebuild OpenSimulator via the [[OSSL_Script_Library/ModInvoke]] mechanism.

@@ Line 17: / Line 17: @@
 == Integration through region modules ==
-OpenSimulator provides a [[region module|IRegionModule]] mechanism by which C# code can directly affect the objects in a region and can interface with any external system.  Interfacing with internal OpenSimulator code is unfortunately something of a black art, though the core distribution itself contains a large number of region modules and test code which can give examples of how to do this.
+OpenSimulator provides a [[region module|IRegionModule]] mechanism by which C# code can directly affect the objects in a region and can interface with any external system.  Using internal OpenSimulator code from a module is currently something of a black art, though the core distribution itself contains a large number of region modules and test code which can give examples of how to do this.  Also, as OpenSimulator is alpha code one has to expect that internal methods will change between releases with no warning.  This will remain the case until individual interfaces are formalized and/or OpenSimulator is considered in beta state.
 Region modules can also send and receive information from scripts via the [[OSSL_Script_Library/ModSendCommand]] mechanism.  In a future OpenSimulator release (0.7.4), region modules will also be able to make custom scripting functions available to scripts without having to manually patch and rebuild OpenSimulator via the [[OSSL_Script_Library/ModInvoke]] mechanism.

← Older revision		Revision as of 23:41, 19 July 2012
Line 10:		Line 10:

	Media on a prim (MOAP), also called Shared Media by Linden Lab, allows you to display and interact with any webpage on the surface of an object with version 2 and later Linden Lab viewers and third party viewers such as Firestorm and Kokua. See [http://community.secondlife.com/t5/English-Knowledge-Base/Shared-Media/ta-p/700145 this page] for more details.		Media on a prim (MOAP), also called Shared Media by Linden Lab, allows you to display and interact with any webpage on the surface of an object with version 2 and later Linden Lab viewers and third party viewers such as Firestorm and Kokua. See [http://community.secondlife.com/t5/English-Knowledge-Base/Shared-Media/ta-p/700145 this page] for more details.
		+
		+	== Integration through Linden Scripting Language (LSL) scripts ==
		+
		+	LSL provides a number of mechanisms for objects in a region to send (e.g. [http://lslwiki.net/lslwiki/wakka.php?wakka=llHTTPRequest llHTTPRequest()]) and receive data (e.g. [http://wiki.secondlife.com/wiki/LlRequestURL llRequestURL()] and then the http_request event) from external servers via HTTP. Please see the linked webpages for more details on using these and associated commands.
		+
		+	== Integration through region modules ==
		+
		+	OpenSimulator provides a [[region module\|IRegionModule]] mechanism by which C# code can directly affect the objects in a region and can interface with any external system. Interfacing with internal OpenSimulator code is unfortunately something of a black art, though the core distribution itself contains a large number of region modules and test code which can give examples of how to do this.
		+
		+	Region modules can also send and receive information from scripts via the [[OSSL_Script_Library/ModSendCommand]] mechanism. In a future OpenSimulator release (0.7.4), region modules will also be able to make custom scripting functions available to scripts without having to manually patch and rebuild OpenSimulator via the [[OSSL_Script_Library/ModInvoke]] mechanism.

@@ Line 1: / Line 1: @@
 = Introduction =
-*** This page is a work-in-progress ***
+'''This page is a work-in-progress'''
 Integrating OpenSimulator regions with external sources of data can be done in a number of ways.

@@ Line 7: / Line 7: @@
 = Techniques =
-== Shared media/media on a prim.
+== Shared media/media on a prim ==
 Media on a prim (MOAP), also called Shared Media by Linden Lab, allows you to display and interact with any webpage on the surface of an object with version 2 and later Linden Lab viewers and third party viewers such as Firestorm and Kokua.  See [http://community.secondlife.com/t5/English-Knowledge-Base/Shared-Media/ta-p/700145 this page] for more details.

RegionIntegration - Revision history

Justincc: /* Integration through region modules */

Justincc: /* Integration through region modules */

Justincc: /* Techniques */

Justincc: /* Introduction */

Justincc: /* Techniques */

Justincc: Created page with "= Introduction = *** This page is a work-in-progress *** Integrating OpenSimulator regions with external sources of data can be done in a number of ways. = Techniques = == Sh..."

Justincc: Created page with "= Introduction = * This page is a work-in-progress * Integrating OpenSimulator regions with external sources of data can be done in a number of ways. = Techniques = == Sh..."