Difference between revisions of "LlOpenRemoteDataChannel"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
m (Fixed some typos) |
m (lsl code tagging) |
||
| Line 11: | Line 11: | ||
** May be advisable to somewhat regularly (before expected use or on a regular schedule) check that the channel is good and hasn't changed by calling llOpenRemoteDataChannel and comparing to the previous channel. | ** May be advisable to somewhat regularly (before expected use or on a regular schedule) check that the channel is good and hasn't changed by calling llOpenRemoteDataChannel and comparing to the previous channel. | ||
|constants | |constants | ||
|examples=< | |examples=<lsl> | ||
default | default | ||
{ | { | ||
| Line 29: | Line 29: | ||
} | } | ||
} | } | ||
</ | </lsl> | ||
|helpers | |helpers | ||
|also_functions | |also_functions | ||
Revision as of 05:17, 29 March 2008
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Summary
Function: llOpenRemoteDataChannel( );| 254 | Function ID |
| 1.0 | Forced Delay |
| 10.0 | Energy |
Creates a channel to listen for XML-RPC calls. Will trigger a remote_data event with channel id once it is available.
Caveats
- This function causes the script to sleep for 1.0 seconds.
- If an object moves from one region to another it must re-open the channel
- The object will get the *same* channel as before, but without re-opening no requests will get through
- Any channel that is not used for 14 days will be cleaned up.
- May be advisable to somewhat regularly (before expected use or on a regular schedule) check that the channel is good and hasn't changed by calling llOpenRemoteDataChannel and comparing to the previous channel.
Examples
<lsl> default {
state_entry()
{
llOpenRemoteDataChannel();
}
changed(integer c)
{
if(c & (CHANGED_REGION