Dataserver

Triggered when task receives asynchronous data

• 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.

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);
 
            }
        }
    }
}

• Requesting data from within the dataserver event is quite valid. However, be aware not to make your own loop inside the event. It will lock the event open until the loop is finished then send all the requests made from within, with the data from the first retrieval.

Issues

SVC-2596

[c]

Script dataserver events become permanently blocked until sim restart