Difference between revisions of "GenerateKey"

From Second Life Wiki
Jump to navigation Jump to search
 
Line 3: Line 3:
|func_desc=Generates a key using Type 3 (MD5) UUID generation to create a unique key using region-name, object-key, service and variable.
|func_desc=Generates a key using Type 3 (MD5) UUID generation to create a unique key using region-name, object-key, service and variable.


'''NOTE:''' this function has been largely superseded by [[llGenerateKey]]() which is faster; however, the implementation on this page does have some further uses, as it is able to generate predictable random keys which is useful if you wish to avoid the need to track lists of recent keys, for example if two scripts are communicating within the same prim.
'''NOTE:''' this function has been largely superseded by [[llGenerateKey]]() which is faster; however, the implementation on this page does have some further uses, as it is able to generate predictable random keys which is useful if you wish to avoid the need to track lists of recent keys. For example, using the optimised form of this function, two scripts using the same URI for key generation can produce the same set of keys using a synchronised variable, useful for generating a new key for each message, that can be predicted ahead of time (rather than keeping a list of recent keys to ignore).
|return_type=key
|return_type=key
|return_text=The generated key
|return_text=The generated key
Line 11: Line 11:
|cat1=Examples
|cat1=Examples
|cat2=Library
|cat2=Library
|examples=In a two-prim linked-set put the following script (adding generateKey where noted) into the child-prim:<lsl>integer requestID = 0;
|examples=In a two-prim linked-set put the following script (adding generateKey where noted) into the child-prim:
<source lang="lsl2">integer requestID = 0;


// Add generateKey here!!
// Add generateKey here!!
Line 29: Line 30:
             llOwnerSay("Request: " + (string)id + " = " + msg);
             llOwnerSay("Request: " + (string)id + " = " + msg);
     }
     }
}</lsl>And the following script in the root-prim:<lsl>default {
}</source>
 
And the following script in the root-prim:
 
<source lang="lsl2">default {
     link_message(integer x, integer y, string msg, key id) {
     link_message(integer x, integer y, string msg, key id) {
         if (y == 1234) // Echo, send straight back
         if (y == 1234) // Echo, send straight back
             llMessageLinked(x, y, msg, id);
             llMessageLinked(x, y, msg, id);
     }
     }
}</lsl>Simply touch the child-prim to use, enjoy!
}</source>
 
Simply touch the child-prim to use, enjoy!
}}
}}


= Implementation =
= Implementation =
<lsl>key generateKey(string service, string variable) {
<source lang="lsl2">key generateKey(string service, string variable) {
     return (key)llInsertString(
     return (key)llInsertString(
         llInsertString(
         llInsertString(
Line 64: Line 71:
         "-"
         "-"
     );
     );
}</lsl>
}</source>


= Optimisation =
= Optimisation =
Line 70: Line 77:


Here is an example of the caching version of the function:
Here is an example of the caching version of the function:
<lsl>string uri;
<source lang="lsl2">string uri;
key generateKey(string service, string variable) {
key generateKey(string service, string variable) {
     if (uri == "")  
     if (uri == "")  
Line 115: Line 122:
         llOwnerSay("Random key of the moment is \"" + (string)generateKey("counter", (string)(counter++)) + "\"");
         llOwnerSay("Random key of the moment is \"" + (string)generateKey("counter", (string)(counter++)) + "\"");
     }
     }
}</lsl>
}</source>


{{LSLC|Examples}}
{{LSLC|Examples}}

Latest revision as of 04:24, 23 January 2015

Summary

Function: key GenerateKey( string service, string variable );

Generates a key using Type 3 (MD5) UUID generation to create a unique key using region-name, object-key, service and variable.

NOTE: this function has been largely superseded by llGenerateKey() which is faster; however, the implementation on this page does have some further uses, as it is able to generate predictable random keys which is useful if you wish to avoid the need to track lists of recent keys. For example, using the optimised form of this function, two scripts using the same URI for key generation can produce the same set of keys using a synchronised variable, useful for generating a new key for each message, that can be predicted ahead of time (rather than keeping a list of recent keys to ignore).
Returns a key The generated key

• string service The service, object, function, or whatever else this key may represent.
• string variable Any variable(s) relevant to the service that uniquely distinguish it.

Examples

In a two-prim linked-set put the following script (adding generateKey where noted) into the child-prim:

integer requestID = 0;

// Add generateKey here!!

default {
    touch_start(integer x) {
        llMessageLinked(
            LINK_ROOT, 
            1234, 
            "I am a request", 
            generateKey("echo", (string)requestID++)
        );
    }

    link_message(integer x, integer y, string msg, key id) {
        if (y == 1234) 
            llOwnerSay("Request: " + (string)id + " = " + msg);
    }
}

And the following script in the root-prim:

default {
    link_message(integer x, integer y, string msg, key id) {
        if (y == 1234) // Echo, send straight back
            llMessageLinked(x, y, msg, id);
    }
}
Simply touch the child-prim to use, enjoy!

Implementation

key generateKey(string service, string variable) {
    return (key)llInsertString(
        llInsertString(
            llInsertString(
                llInsertString(
                    llMD5String(
                        "secondlife://" + llGetRegionName()  + "/" + 
                            (string)llGetKey() + "/" + 
                            (string)llGetLinkNumber() + "/" + 
                            llGetScriptName() + "/" + 
                            service + "/" + variable, 
                        0 // This is reserved by specification, will 
                          // be increased with new/different versions.
                    ),
                    8,
                    "-"
                ),
                13,
                "-"
            ),
            18,
            "-"
        ),
        23,
        "-"
    );
}

Optimisation

Instead of always calling llGetRegionName(), llGetKey(), llGetLinkNumber(), and llGetScriptName(), you may wish to cache their return values into a uri variable, and only dynamically add the service and variable parameters each-time. Remember to update this variable when you know it's components will have changed, using the changed(), on_rez(), and/or attach() events.

Here is an example of the caching version of the function:

string uri;
key generateKey(string service, string variable) {
    if (uri == "") 
        uri =  "secondlife://" + llGetRegionName()  + "/" + 
            (string)llGetKey() + "/" + 
            (string)llGetLinkNumber() + "/" + 
            llGetScriptName() + "/";
    return (key)llInsertString(
        llInsertString(
            llInsertString(
                llInsertString(
                    llMD5String(
                        uri + service + "/" + variable, 
                        0 // This is reserved by specification, will 
                          // be increased with new/different versions.
                    ),
                    8,
                    "-"
                ),
                13,
                "-"
            ),
            18,
            "-"
        ),
        23,
        "-"
    );
}

integer counter = 0;
default {
    state_entry() {
        llSetTimerEvent(10.0);
    }

    on_rez(integer x) { uri = ""; }
    attach(key id) { uri = ""; }
    changed(integer changes) {
        if (changes & (CHANGED_REGION | CHANGED_INVENTORY)) uri = "";
    }

     timer() {
        llOwnerSay("Random key of the moment is \"" + (string)generateKey("counter", (string)(counter++)) + "\"");
    }
}