Difference between revisions of "LlOpenRemoteDataChannel"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
Kelly Linden (talk | contribs) |
Kelly Linden (talk | contribs) |
||
Line 6: | Line 6: | ||
|return_text | |return_text | ||
|spec | |spec | ||
|caveats | |caveats=* If an object moves from one region to another it must re-open the channel | ||
* 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-opnening no requests will get through | ** The object will get the *same* channel as before, but without re-opnening no requests will get through | ||
* Any channel that is not used for 14 days will be cleaned up. | * Any channel that is not used for 14 days will be cleaned up. |
Revision as of 12:58, 12 April 2007
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-opnening 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 shedule) check that the channel is good and hasn't changed by calling llOpenRemoteDataChannel and comparing to the previous channel.