LlGetSimulatorHostname

2013-06-24T15:54:37Z

Silky Mesmeriser:

{{LSL_Function
|func_id=283|func_sleep=10.0|func_energy=10.0
|func=llGetSimulatorHostname
|return_type=string
|func_footnote
|func_desc
|return_text=that is the hostname of the machine the script is running on (same as string in viewer Help dialog)
|spec
|caveats
|constants
|examples=<lsl>
// The beginnings of a region-info script.
string region;
string sim;

default
{
state_entry()
{
llSetTimerEvent(1.0);
}
timer()
{
string here = llGetRegionName();
if(region != here)
{
sim = llGetSimulatorHostname();
region = here;
}
llSetText(
" REGION NAME : " + region +
"\n SIM HOSTNAME : " + sim +
"\nTIME DIALATION : " + (string)llGetRegionTimeDilation() +
"\n REGION FPS : " + (string)llGetRegionFPS(),
<0,1,0>, 1.0);
}
}
</lsl>
<lsl>
// Alternative method by Silky Mesmeriser
// This example is more complex than the direct llGetSimulatorHostname() call however it avoids the
// imposed delay of the ll function and is useful sometimes if the undue delay is a problem for your
// script. Of course HTTP transactions to third party services like this can fail at times thus this
// example will fall back to the LSL function with it's delay if it is unable to successfully get
// the hostname from the selected third party source.

string HOSTNAME_URI = "http://www.displaymyhostname.com/"; // URL to grab hostname from
string HOSTNAME_START = "<div class=\"hostname\">"; // What to look for before the hostname string
string HOSTNAME_END = "</div>"; // What marks the end of the hostname string

// Variable to store the simulator hostname set initially to Pending... to inform the end user
// if they request the information from the object prior to successful retrieval.
string g_sSimHost = "Pending...";
key g_kHostReqID; // Variable to store the HTTP request ID so we can handle the correct http_response

string smReadHostname(string sData)
{ // Parse the reply from the remote server and grab the hostname
integer iIndex = llSubStringIndex(sData, HOSTNAME_START);
sData = llGetSubString(sData, iIndex + llStringLength(HOSTNAME_START), llStringLength(sData));
iIndex = llSubStringIndex(sData, HOSTNAME_END);
sData = llGetSubString(sData, 0, iIndex -1);
// Sanity check the hostname it should end with .lindenlab.com and not contain any characters like spaces or newlines
// If this is untrue for some reason it's very likely that something on the page changed making it parse incorrectly
// and thus the result can't be trusted.
if (llSubStringIndex(sData, ".lindenlab.com") != (llStringLength(sData) - llStringLength(".lindenlab.com")) || llSubStringIndex(sData, " ") > -1 || llSubStringIndex(sData, "\n") > -1) sData == "ERROR";
return sData;
}

string smGetSimulatorHostname()
{
// If called before we have a hostname start the request process
if (g_sSimHost == "Pending...") g_kHostReqID = llHTTPRequest(HOSTNAME_URI,[HTTP_METHOD, "GET"], "");
// Return the hostname if available or indicate pending status
return g_sSimHost;
}

default
{
changed(integer iChange)
{ // If the region restarts it may be moved to another simulator this should be the only time we need to check again.
if (iChange & CHANGED_REGION_START) smGetSimulatorHostname();
}

http_response(key kReqID, integer iStatus, list lMeta, string sBody)
{
if (kReqID == g_kHostReqID && iStatus == 200) {
g_sSimHost = smReadHostname(sBody);
if (g_sSimHost == "ERROR")
{ // The hostname doesn't seem to be parsing properly so lets inform the user and fall back to the LSL function
llOwnerSay("API error determining simulator hostname, falling back to LSL method this will take a few seconds due to imposed limitations in LSL");
g_sSimHost = llGetSimulatorHostname();
}
} else if (kReqID == g_kHostReqID) { // The HTTP status code indicates something went wrong we inform the user and fall back to the LSL function to be safe
llOwnerSay("HTTP error determining simulator hostname: HTTP Code " + (string)iStatus + " falling back to LSL method this will take a few seconds due to imposed limitations in LSL");
g_sSimHost = llGetSimulatorHostname();
}
llOwnerSay("Simulator Hostname: " + smGetSimulatorHostname());
}

state_entry()
{
// This begins the HTTP request for the sim hostname I think it makes
// sense to do this right away at startup as there is no need to ask
// every time we want to use it.
smGetSimulatorHostname();
}
}
</lsl>
|helpers
|also_functions={{LSL DefineRow||[[llGetRegionFPS]]|Gets the region FPS}}
{{LSL DefineRow||[[llGetRegionTimeDilation]]|Gets the region time dilation}}
|also_tests
|also_events
|also_articles={{LSL DefineRow||[[Simulator IP Addresses]]|}}
|notes
|cat1=Region
|cat2
|cat3
|cat4
}}

Talk:LSL3

2010-05-27T09:54:27Z

Silky Mesmeriser:

I'd add the to this the switch/case statement. SInce LSL isn't a run-time scripting language, per se, it should be quite possible to at least allow optimizations for switch(integer) situations and switch(string) would at least allow programming clarity, even if no other optimization was done.

The other proposed changes I listed in the jira also have merit, though perhaps the single most important would be a provision for a common library of functions beyond what LL defines. New functions could be added on a a regular basis after vetting by the community and LL within a cc* namespace. Perhaps a cc.* namespace to make 100% certain of backwards compatability. [[User:Saijanai Kuhn|Saijanai]] 07:38, 24 February 2008 (PST)

I'm not sure if this has previously been suggested but it would be useful as an add on to dialog menus to be able to request text input from the user though a similar interface perhaps through a function like llGetTextInput would save having to open listeners and essentially break out of the menu to a completely different method of input which is at best a little confusing. I appreciate this would probably need a small addition to the viewer as well, but as a new viewer is under development then perhaps that functionality could be included in preparation. [[User:Silky Mesmeriser|Silky Mesmeriser]] 09:54, 27 May 2010 (UTC)

== Better support for other spoken human languages ==

Here's a constant in a script for a message in English.

MsgAlreadyGiven = "Not found, perhaps already given out?";

Now, here's the same constant, in French and Italian.

MsgAlreadyGiven = "Pas trouve, peut-etre deja enleve?";
MsgAlreadyGiven = "Non trovato, forse gia dato?";

In French and Italian there, it's wrong, though.

It's wrong because LSL forced me to drop the accents, which creates spelling mistakes, forcing me to look illiterate in a multitude of languages. While that has a certain rakish appeal to it :} if there's another version of LSL, it really needs to be able to handle accents. I know lots of unilingual anglophone programmers will pshaw this idea, but still. [[User:Chaz Longstaff|Chaz Longstaff]] 08:25, 24 February 2008

:The compiler supports accented characters, the font used by the editor doesn't show them. {{JIRA|VWR-3857}} -- [[User:Strife Onizuka|Strife Onizuka]] 04:48, 25 February 2008 (PST)

::last i checked, characters like ç and ã displayed on the script editor just fine (hell, even stuff like φ, ▅ and ░ show as expected), but when saving it would give an error (often pointing to the wrong point on the script as the source of the error), the solution I found was to use llUnEscapeURL for inputing such characters on the script code (but since it ias afunction, it won't work unles run inside an state), to figure out what is the code to an specific charater, one way would be having a script tel you the escaped version of what it hears and say to it the characters you want the escape code for, then use the returned code on yoru script--[[User:TigroSpottystripes Katsu|TigroSpottystripes Katsu]] 23:58, 25 February 2008 (PST)

:::I thought they had that bug fixed ~_~ -- [[User:Strife Onizuka|Strife Onizuka]] 04:42, 26 February 2008 (PST)

== Less aggressive/smarter generation of function delays. ==

Some functions have pointful but painfully long delays attached to them to prevent abuse. But by stalling the script for long periods of time you train people to break the function out into seperate linkmessaged scripts, at which point its alot easier for them to start multiplying them to outright defeat the delay, which creates more load.

I suggest making most of those functions /not/ delay unless they get called twice in a delaylength period of time, in which case the function can silently pause for the remainder of the expected time before carrying on.

Of course it creates situations where otherwise instantaneous functions can be laggy in effect if being called rapidfire with soon-to-be-outdated arguments, but I feel its a much better alternative to what we have now. If its a big enough problem people can load in their own explicit delays. --[[User:Elbereth Witte|Elbereth Witte]] 20:30, 27 June 2009 (UTC)

Second Life Wiki - User contributions [en]

LlGetSimulatorHostname

Talk:LSL3