Second Life Wiki - User contributions [en]

Dataserver

2009-08-18T14:28:47Z

Skwiggs Skytower:

{{Issues/SVC-2596}}{{LSL_Event
|event_id=24|event_delay|event=dataserver
|p1_type=key|p1_name=queryid|p1_desc=matches the return of the requesting function
|p2_type=string|p2_name=data|p2_desc=the requested data (cast as a string as necessary).
|event_desc=Triggered when task receives asynchronous data
|constants
|spec
|constants={{{!}} {{Prettytable|style=margin-top:0;}}
{{!}}- {{Hl2}}
! Function
! colspan="2" {{!}}Input
! Decode
! colspan="4" {{!}} Description
{{!}}-
{{!}} colspan="3" {{!}} [[llGetNotecardLine]]
{{!}} {{LSLG|string}}
{{!}} colspan="4" {{!}} The line in the requested notecard, limited to 255 bytes.<br/>If [[EOF]] the line requested is past the end of the notecard.
{{!}}-
{{!}} colspan="3" {{!}} [[llGetNumberOfNotecardLines]]
{{!}} ([[integer]])
{{!}} colspan="4" {{!}} The number of lines in the notecard requested.
{{!}}-
{{!}} rowspan="7" {{!}} [[llRequestAgentData]]
{{LSL Constants/llRequestAgentData}}
{{!}}-
{{!}} rowspan="1" {{!}} [[llRequestInventoryData]]
{{LSL Constants/llRequestInventoryData}}
{{!}}-
{{!}} rowspan="9" {{!}} [[llRequestSimulatorData]]
{{LSL Constants/llRequestedSimulatorData}}
{{!}}}
|caveats=
*Dataserver answers do not necessarily come in the order they were requested.
**If there are multiple pending requests, always use the queryid key to determine which answer is being received.
*Dataserver requests will trigger '''dataserver''' events in all scripts within the same prim where the request was made.
**If there are multiple scripts with '''dataserver''' events in the same prim, always use the queryid key to determine which answer is being received.
**'''dataserver''' events will not be triggered in scripts contained in other prims in the same linked object.
*If more data is requested using the same query_id before the '''dataserver''' event dealing with that query_id has resolved the data will be trashed. To avoid the trashing do not ask [[if]](query_key == query_id). Though (see above caveats) this has its own drawbacks.
|notes=*Requesting a dataserver event from within a dataserver event is a very valid use of this function. Be aware not to make your own loop inside the event. It will lock the event open till the loop is finished then send all the requests made, from within, with the data from the first retrieval.
|examples=<lsl>key kQuery;
integer iLine = 0;
default {

state_entry() {
llSay(0, "Reading notecard...");
kQuery = llGetNotecardLine("My Notecard", iLine);
}

dataserver(key query_id, string data) {

if (query_id == kQuery) {
// this is a line of our notecard
if (data == EOF) {

llSay(0, "No more lines in notecard, read " + (string)iLine + " lines.");

} else {

// increment line count
llSay(0, "Line " + (string)iLine + ": " + data);

//request next line
++iLine;
kQuery = llGetNotecardLine("My Notecard", iLine);

}
}
}
}</lsl>
|helpers
|also_header
|also_events
|also_functions
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Dataserver
|cat2=Notecard
|cat3=Inventory
|cat4=Region
|cat5=Script
|cat6=Prim
}}

Dataserver

2009-08-18T13:57:28Z

Skwiggs Skytower:

{{Issues/SVC-2596}}{{LSL_Event
|event_id=24|event_delay|event=dataserver
|p1_type=key|p1_name=queryid|p1_desc=matches the return of the requesting function
|p2_type=string|p2_name=data|p2_desc=the requested data (cast as a string as necessary).
|event_desc=Triggered when task receives asynchronous data
|constants
|spec
|constants={{{!}} {{Prettytable|style=margin-top:0;}}
{{!}}- {{Hl2}}
! Function
! colspan="2" {{!}}Input
! Decode
! colspan="4" {{!}} Description
{{!}}-
{{!}} colspan="3" {{!}} [[llGetNotecardLine]]
{{!}} {{LSLG|string}}
{{!}} colspan="4" {{!}} The line in the requested notecard, limited to 255 bytes.<br/>If [[EOF]] the line requested is past the end of the notecard.
{{!}}-
{{!}} colspan="3" {{!}} [[llGetNumberOfNotecardLines]]
{{!}} ([[integer]])
{{!}} colspan="4" {{!}} The number of lines in the notecard requested.
{{!}}-
{{!}} rowspan="7" {{!}} [[llRequestAgentData]]
{{LSL Constants/llRequestAgentData}}
{{!}}-
{{!}} rowspan="1" {{!}} [[llRequestInventoryData]]
{{LSL Constants/llRequestInventoryData}}
{{!}}-
{{!}} rowspan="9" {{!}} [[llRequestSimulatorData]]
{{LSL Constants/llRequestedSimulatorData}}
{{!}}}
|caveats=
*Dataserver answers do not necessarily come in the order they were requested.
**If there are multiple pending requests, always use the queryid key to determine which answer is being received.
*Dataserver requests will trigger '''dataserver''' events in all scripts within the same prim where the request was made.
**If there are multiple scripts with '''dataserver''' events in the same prim, always use the queryid key to determine which answer is being received.
**'''dataserver''' events will not be triggered in scripts contained in other prims in the same linked object.
*If more data is requested using the same query_id before the '''dataserver''' event dealing with that query_id has resolved the data will be trashed. To avoid the trashing do not ask [[if]](query_key == query_id). Though (see above caveats) this has its own drawbacks.
*Requesting a dataserver event from within a dataserver event is a very valid use of this function. Be aware not to make your own loop inside the event. It will lock the event open till the loop is finished then send all the requests made, from within, with the data from the first retrieval.
|examples=<lsl>key kQuery;
integer iLine = 0;
default {

state_entry() {
llSay(0, "Reading notecard...");
kQuery = llGetNotecardLine("My Notecard", iLine);
}

dataserver(key query_id, string data) {

if (query_id == kQuery) {
// this is a line of our notecard
if (data == EOF) {

llSay(0, "No more lines in notecard, read " + (string)iLine + " lines.");

} else {

// increment line count
llSay(0, "Line " + (string)iLine + ": " + data);

//request next line
++iLine;
kQuery = llGetNotecardLine("My Notecard", iLine);

}
}
}
}</lsl>
|helpers
|also_header
|also_events
|also_functions
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Dataserver
|cat2=Notecard
|cat3=Inventory
|cat4=Region
|cat5=Script
|cat6=Prim
}}