OsMessageObject - Revision history

Ubit at 20:05, 27 October 2021

2021-10-27T20:05:45Z

2021-10-27T20:03:30Z

2021-10-27T19:59:32Z

2021-10-27T19:59:18Z

2021-10-27T19:58:44Z

2021-10-27T19:58:11Z

2021-10-27T19:54:30Z

Add uppercase

2021-10-27T19:48:25Z

2021-10-27T19:44:01Z

2021-10-27T19:40:31Z

@@ Line 48: / Line 48: @@
 <div style="background-color:#FFA500; padding:10px; padding-bottom:5px; border: 1px #FF544F solid">
 This is incompatible with the normal use of dataserver event on scripts on the receiving prim.<br>
-The dataserver query_id argument should be a unique id of a request. This function just uses it as a sender id. All scripts with dataserver event will receive it with no easy to validate. A normal request may also trigger the event on several scripts of the prim. The target one can compare the query_id and validate it, other scripts can not tell if it is a normal request for other script, or a message
+The dataserver query_id argument should be a unique id of a request. This function just uses it as a sender id. All scripts with dataserver event will receive it with no easy to validate. A normal request may also trigger the event on several scripts of the prim. The target one can compare the query_id and validate it, other scripts can not tell if it is a normal request for other script, or a message.<br>
 </div>
+|
 }}

@@ Line 48: / Line 48: @@
 <div style="background-color:#FFA500; padding:10px; padding-bottom:5px; border: 1px #FF544F solid">
 This is incompatible with the normal use of dataserver event on scripts on the receiving prim.<br>
-The dataserver query_id argument should be a unique id of a request. This function just uses it as a sender id. A normal request may trigger the event on several scripts of the prim. The target one can compare the query_id and validate it, other scripts can not tell if it is a normal request for other script, or a message
+The dataserver query_id argument should be a unique id of a request. This function just uses it as a sender id. All scripts with dataserver event will receive it with no easy to validate. A normal request may also trigger the event on several scripts of the prim. The target one can compare the query_id and validate it, other scripts can not tell if it is a normal request for other script, or a message
 </div>
+|
 }}

@@ Line 43: / Line 43: @@
 |description=
 ''primID'' = the UUID of the prim you are messaging.
-''message'' = The tring you want to send.
+''message'' = The string you want to send.
 Sends a message to a prim identified by the given UUID, a script in the prim must implement the dataserver event handler. the dataserver event is passed the UUID of the calling prim and a string message.

@@ Line 43: / Line 43: @@
 |description=
 ''primID'' = the UUID of the prim you are messaging.
-''message'' = The String of data you want to send.
+''message'' = The tring you want to send.
 Sends a message to a prim identified by the given UUID, a script in the prim must implement the dataserver event handler. the dataserver event is passed the UUID of the calling prim and a string message.

@@ Line 42: / Line 42: @@
 </source>
 |description=
- ''primID'' = the UUID of the prim you are messaging.
+''primID'' = the UUID of the prim you are messaging.
 ''message'' = The String of data you want to send.
- ''message'' = The String of data you want to send.
 Sends a message to a prim identified by the given UUID, a script in the prim must implement the dataserver event handler. the dataserver event is passed the UUID of the calling prim and a string message.

@@ Line 3: / Line 3: @@
 |permissions=${OSSL&#124;osslParcelOG}ESTATE_MANAGER,ESTATE_OWNER
 |delay=0
-|function_syntax= osMessageObject(key objectID, string message)
+|function_syntax= osMessageObject(key primID, string message)
-|ossl_example=This example consists of a sender script, and a reciever script.
+|ossl_example=This example consists of a sender script, and a receiver script.
 : '''Sender script'''
 <source lang = "lsl">
 // ----------------------------------------------------------------
 // Example / Sample Script to show function use.
 //
 default
@@ Line 47: / Line 26: @@
-: '''Reciever script'''
+: '''Receiver script'''
 <source lang = "lsl">
 // Place this script in the Receiver prim.
@@ Line 63: / Line 42: @@
 </source>
 |description=
-Where ''objectID'' = the UUID of the object you are messaging.
+ ''primID'' = the UUID of the prim you are messaging.
-Where ''message'' = The String of data you want to send.
+ ''message'' = The String of data you want to send.
 Sends a message to a prim identified by the given UUID, a script in the prim must implement the dataserver event handler. the dataserver event is passed the UUID of the calling prim and a string message.

@@ Line 69: / Line 69: @@
 Sends a message to to object identified by the given UUID, a script in the object must implement the dataserver function the dataserver function is passed the UUID of the calling prim and a string message.
 <div style="background-color:#FFA500; padding:10px; padding-bottom:5px; border: 1px #FF544F solid">
-This is incompatible with the normal use of dataserver event on scripts the receiving prim.<br>
+This is incompatible with the normal use of dataserver event on scripts on the receiving prim.<br>
-the dataserver query_Id argument should be a unique id of a request. This function just uses it as a sender id, making it impossible to valdidate.
+the dataserver query_id argument should be a unique id of a request. This function just uses it as a sender id. A normal request may trigger the event on several scripts of the prim. The target one can compare the query_id and validate it, other scripts can not tell if it is a normal request for other script, or a message
 </div>
+|
 }}