llKeysKeyValue

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/fr Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

KeysKeyValue

llKeysKeyValue

Summary

Function: key llKeysKeyValue( integer first, integer count );

	Forced Delay
	Energy

Start an asynchronous transaction to request a number of keys.
Returns a handle (a key) that can be used to identify the corresponding dataserver event to determine if this command succeeded or failed.

• integer	first	–	Zero-based index of the first key to retrieve
• integer	count	–	Number of keys to retriever

The dataserver callback parameters are:

• A key containing the handle returned from llKeysKeyValue
• A string containing a comma-delimited list. The first item is a boolean specifying if the transaction succeeded (1) or not (0). On a success result the remaining items are key names. This function will attempt to retrieve the number requested but may return less if there are not enough to fulfill the full amount requested or if the list is too large. The order keys are returned is not guaranteed but is stable between subsequent calls as long as no keys are added or removed. The error XP_ERROR_KEY_NOT_FOUND is returned if there index given is greater than or equal to the number of keys.

Specification

Dataserver

The dataserver callback parameters are:

• A key containing the handle returned from llKeysKeyValue
• A string containing a comma-delimited list (cdl). llDumpList2String([ integer success ] + components);
  • components vary depending upon success or failure of request.
  • Failure: cdl = llDumpList2String([ 0, integer error],",")
  • Success: cdl = llDumpList2String([ 1 ] + key_names),",")

String Components

• integer	success	–	A boolean specifying if the transaction succeeded (1) or not (0).
• integer	error	–	An XP_ERROR_* flag that describes why the operation failed.
• list	key_names

Examples

<lsl>key trans; default {

   state_entry()
   {
       // retrieve the first 10 keys
       trans = llKeysKeyValue(0, 10);
   }

}

dataserver(key t, string value) {

   if (t == trans)
   {
       // our llKeyCountKeyValue transaction is done
       list result = llCSV2List(value);
       if (llList2Integer(result, 0) == 1)
       {
           llSay(0, "Keys retrieved: "+llGetSubString(value, -1);
       }
       else if (llList2String(result, 1) == "key doesn't exist")
       {
           // no more keys
           llSay(0, "No more keys" );
       }
       else
       {
           // keys request failed
           llSay(0, "Key-value failed to request keys: " + llList2String(result, 1) );
       }
   } 

}</lsl>

See Also

Functions

• llGetExperienceErrorMessage
• llCreateKeyValue
• llReadKeyValue
• llUpdateKeyValue
• llDeleteKeyValue
• llDataSizeKeyValue
• llKeyCountKeyValue
• llKeysKeyValue

Deep Notes

Signature
function key llKeysKeyValue( integer first, integer count );