Communication Protocols
From OpenSimulator
(New page: {{Warning|This page is still under construction. Need to slowly fill out the details on the protocols of each type -- ~~~~}} =Introduction= There are a large number of communication pro...) |
(→Simulator to external protocols) |
||
Line 19: | Line 19: | ||
== Simulator to external protocols == | == Simulator to external protocols == | ||
− | There are some ways in which the simulator can be examined or controlled externally. One example of control is the [[RemoteAdmin]] interface. | + | There are some ways in which the simulator can be examined or controlled externally. One example of control is the [[RemoteAdmin]] interface. There are also facilities for [[Monitoring]] the current state of the simulator. |
Revision as of 11:15, 10 October 2011
This page is still under construction. Need to slowly fill out the details on the protocols of each type -- Justincc 20:28, 25 July 2011 (UTC) |
Contents |
Introduction
There are a large number of communication protocols used by OpenSimulator. These can be divided into the four types.
Client protocols
These are communication protocols between the server and a client/viewer. The primary protocol here is the Linden Lab viewer protocol. This protocol is divided into UDP messages (such as object updates, avatar position updates, etc.) and HTTP based messages via capabilities.
Grid service protocols
On a standalone OpenSimulator installation, all communications occurs within process. However, with a grid installation the simulators need to communicate with backend services (asset, inventory, etc.). This is done over HTTP.
Simulator to simulator protocols
There are some situations in which simulators need to communicate directly with one another. One of these is on teleport or region crossing. This communication is carried out through HTTP.
Simulator to external protocols
There are some ways in which the simulator can be examined or controlled externally. One example of control is the RemoteAdmin interface. There are also facilities for Monitoring the current state of the simulator.