Difference between revisions of "Region"
(LSL scripts are generally sim specific, and can't easily roam across the grid) |
(grossly inaccurate.) |
||
Line 1: | Line 1: | ||
The land in SL is hosted on dual-core dual-cpu Linux servers. Each region is 65,536 m² (256x256m), there are two types of regions: Normal and Void. A server hosting normal regions hosts two regions, one per cpu{{Footnote|1={{KB|4235|Information about Openspaces (Void Regions)}}|handle=cpu}}. On the other hand void regions are hosted 4 per cpu but support fewer prims and users{{Footnote/dup|cpu}}. | |||
To learn more about the servers hosting SL, you can read the series of articles [http://blog.secondlife.com/?s=%22class+5%22 | To learn more about the servers hosting SL, you can read the series of articles that have been posted to the [http://blog.secondlife.com/?s=%22class+5%22 SL blog]. | ||
== Effects on Scripting == | |||
Scripts can detect their current region, and can detect region changes, but these factors are normally separate from region coordinates. There is a delay associated with an object moving from one region to another, this happens because object and all of it's scripts states must be serialized, sent to the new region, and deserialized. | |||
== Footnotes == | |||
{{Footnotes}} | |||
Revision as of 00:02, 29 May 2008
The land in SL is hosted on dual-core dual-cpu Linux servers. Each region is 65,536 m² (256x256m), there are two types of regions: Normal and Void. A server hosting normal regions hosts two regions, one per cpu<sup class="TablePager_nav" style="font-size:75%;" id="fn_1" title="[KB]">[1]. On the other hand void regions are hosted 4 per cpu but support fewer prims and users<sup class="TablePager_nav" style="font-size:75%;" id="fn_1" title="[KB]">[1].
To learn more about the servers hosting SL, you can read the series of articles that have been posted to the SL blog.
Effects on Scripting
Scripts can detect their current region, and can detect region changes, but these factors are normally separate from region coordinates. There is a delay associated with an object moving from one region to another, this happens because object and all of it's scripts states must be serialized, sent to the new region, and deserialized.