Teleports

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
m (Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name)
 
(61 intermediate revisions by one user not shown)
Line 1: Line 1:
__NOTOC__
 
 
{{Quicklinks}}
 
{{Quicklinks}}
<br />
 
  
This page explains the several flavors of teleports in and around opensim. It reflects the code as of the creation of this page. Likely will need updating soon.
+
=Introduction=
  
== Grid Teleport Procedure ==
+
A teleport is the transfer of a user's connection (represented in-world by their avatar) from one location to another.  These locations can be
  
[[Image:GridTeleports.jpg|500px]]
+
* Within the same region.
 +
* Between different regions on the same simulator.
 +
* Between different simulators on the same network within the same grid (e.g. a grid hosted on a single network).
 +
* Between different networks within the same grid (e.g. between simulators hosted on OSGrid).
 +
* Between different networks on different grids (i.e. Hypergrid teleport).
  
== Hypergrid Teleport Procedure ==
+
In OpenSimulator 0.7.5 and for many releases previously, a teleport protocol called SIMULATION/0.1 was used.  In OpenSimulator 0.7.6 and after, a teleport protocol called SIMULATION/0.2 is used by default.  However, OpenSimulator can still use the SIMULATION/0.1 protocol required by older versions and will automatically inter-operate with them.
  
[[Image:HypergridTeleports.jpg|500px]]
+
If you want to know an eye-watering amount of nitty-gritty about how this works, then please see the [[Teleport Protocol]] page.
  
== Open Grid Protocol Teleport Procedure ==
+
=Configuration=
  
See [http://wiki.secondlife.com/wiki/OGP_Explained#Teleport OGP Explained "Teleport"]
+
Normally, no configuration is required. However, from OpenSimulator 0.7.6 onwards, one can force the simulator to always use the older SIMULATION/0.1 protocol to send an avatar to another simulator, receive an avatar from another simulator or both.
  
== Related ==
+
==Using SIMULATION/0.1 to send an avatar to another region==
  
[[Image:Child-event-queue.png|500px]]
+
The protocol version used for outgoing teleports is controlled by the MaxOutgoingTransferVersion attribute in the [EntityTransfer] section of OpenSim.ini. Specifying
  
== Teleports in OpenSimulator as of 2009-02-06 ==
+
[EntityTransfer]
 +
MaxOutgoingTransferVersion = "SIMULATION/0.1"
  
[[Image:Teleport.jpg]]
+
here will make the simulator use this earlier protocol for outgoing teleports even if the destination has SIMULATION/0.2 available (all such simulators should also have SIMULATION/0.1 available). See OpenSimDefaults.ini for more details.
  
== Teleport Study (2009-03-05) ==
+
==Using SIMULATION/0.1 to receive an avatar from another region==
  
The following four pictures compare the current agent transfer scheme with 3 possible agent transfer schemes. The different schemes have slightly different requirements with respect to authentication.
+
In this case, one needs to use the ConnectorProtocolVersion in the [SimulationService] section of StandaloneCommon.ini or GridCommon.ini as appropriate. For example
  
[[Image:TPCurrent.JPG]]
+
[SimulationService]
 +
ConnectorProtocolVersion = "SIMULATION/0.1"
  
[[Image:TPScenarioA.JPG]]
+
=References=
  
[[Image:TPScenarioB.JPG]]
+
* [[Teleport Protocol]] - an extremely in depth look at the teleport protocol.
 
+
[[Image:TPScenarioC.JPG]]
+

Latest revision as of 15:43, 22 October 2013

Contents

[edit] Introduction

A teleport is the transfer of a user's connection (represented in-world by their avatar) from one location to another. These locations can be

  • Within the same region.
  • Between different regions on the same simulator.
  • Between different simulators on the same network within the same grid (e.g. a grid hosted on a single network).
  • Between different networks within the same grid (e.g. between simulators hosted on OSGrid).
  • Between different networks on different grids (i.e. Hypergrid teleport).

In OpenSimulator 0.7.5 and for many releases previously, a teleport protocol called SIMULATION/0.1 was used. In OpenSimulator 0.7.6 and after, a teleport protocol called SIMULATION/0.2 is used by default. However, OpenSimulator can still use the SIMULATION/0.1 protocol required by older versions and will automatically inter-operate with them.

If you want to know an eye-watering amount of nitty-gritty about how this works, then please see the Teleport Protocol page.

[edit] Configuration

Normally, no configuration is required. However, from OpenSimulator 0.7.6 onwards, one can force the simulator to always use the older SIMULATION/0.1 protocol to send an avatar to another simulator, receive an avatar from another simulator or both.

[edit] Using SIMULATION/0.1 to send an avatar to another region

The protocol version used for outgoing teleports is controlled by the MaxOutgoingTransferVersion attribute in the [EntityTransfer] section of OpenSim.ini. Specifying

[EntityTransfer]
MaxOutgoingTransferVersion = "SIMULATION/0.1" 

here will make the simulator use this earlier protocol for outgoing teleports even if the destination has SIMULATION/0.2 available (all such simulators should also have SIMULATION/0.1 available). See OpenSimDefaults.ini for more details.

[edit] Using SIMULATION/0.1 to receive an avatar from another region

In this case, one needs to use the ConnectorProtocolVersion in the [SimulationService] section of StandaloneCommon.ini or GridCommon.ini as appropriate. For example

[SimulationService]
ConnectorProtocolVersion = "SIMULATION/0.1"

[edit] References

Personal tools
General
About This Wiki