LSL Protocol/EasyTalk - Revision history

ObviousAltIsObvious Resident: tag to

2015-01-25T19:40:09Z

← Older revision		Revision as of 12:40, 25 January 2015
Line 30:		Line 30:

	== Serialization / Deserialization ==		== Serialization / Deserialization ==
	<~~lsl~~>		<source lang="lsl2">

	string dumpList(list lst)		string dumpList(list lst)
Line 41:		Line 41:
	}		}

	</~~lsl~~>		</source>


	When needing to send a message use the following:		When needing to send a message use the following:
	<~~lsl~~>		<source lang="lsl2">

	// for linkset:		// for linkset:
Line 52:		Line 52:
	// for say channels:		// for say channels:
	llSay(CHANNEL,dumpList( [ sME, "TEXT", "SHOW", str, vcolor ] );		llSay(CHANNEL,dumpList( [ sME, "TEXT", "SHOW", str, vcolor ] );
	</~~lsl~~>		</source>

	When needing to execute the command do something like:		When needing to execute the command do something like:

	<~~lsl~~>		<source lang="lsl2">
	link_message(integer channel,integer num, string message,key id)		link_message(integer channel,integer num, string message,key id)
	{		{
Line 70:		Line 70:
	// answers only if we are the target		// answers only if we are the target
	if(dst!=sME) return;		if(dst!=sME) return;
	</~~lsl~~>		</source>

	Note the use of sME for each script for rapid deciding it's me.		Note the use of sME for each script for rapid deciding it's me.

Uzume Grigorovich: /* Serialization / Deserialization */ lsl code tagging

2008-03-31T04:45:54Z

Serialization / Deserialization: lsl code tagging

← Older revision		Revision as of 21:45, 30 March 2008
Line 30:		Line 30:

	== Serialization / Deserialization ==		== Serialization / Deserialization ==
	<~~pre~~>		<lsl>

	string dumpList(list lst)		string dumpList(list lst)
Line 41:		Line 41:
	}		}

	</~~pre~~>		</lsl>


	When needing to send a message use the following:		When needing to send a message use the following:
	<~~pre~~>		<lsl>

	// for linkset:		// for linkset:
Line 52:		Line 52:
	// for say channels:		// for say channels:
	llSay(CHANNEL,dumpList( [ sME, "TEXT", "SHOW", str, vcolor ] );		llSay(CHANNEL,dumpList( [ sME, "TEXT", "SHOW", str, vcolor ] );
	</~~pre~~>		</lsl>

	When needing to execute the command do something like:		When needing to execute the command do something like:

	<~~pre~~>		<lsl>
	link_message(integer channel,integer num, string message,key id)		link_message(integer channel,integer num, string message,key id)
	{		{
Line 70:		Line 70:
	// answers only if we are the target		// answers only if we are the target
	if(dst!=sME) return;		if(dst!=sME) return;
	</~~pre~~>		</lsl>

	Note the use of sME for each script for rapid deciding it's me.		Note the use of sME for each script for rapid deciding it's me.

Salahzar Stenvaag: New page: {{LSL Header}} Back to Protocol page ==Easy Talk Protocol == The problem: coordinate object either using llSay or llMessageLinked in a linkset, using a single channel wh...

2008-01-27T12:09:08Z

New page: {{LSL Header}} Back to Protocol page ==Easy Talk Protocol == The problem: coordinate object either using llSay or llMessageLinked in a linkset, using a single channel wh...

New page

{{LSL Header}}
[[LSL Protocol|Back to Protocol page]]

==Easy Talk Protocol ==

The problem: coordinate object either using llSay or llMessageLinked in a linkset, using a single channel where objects can understand:
* sender (who generated the message and shoule be possibly replied)
* destination (to select object who should handle the message)
* command (which action to perform)
* free form parameters

Protocol is implemented using a very simple List/String dumping parsification using the character "|" as separator.
Since this is a very easy protocol I just choose this character which is common on keyboards, but very unlikely to be used in general.
It is also very simple to input in notecards and so you can have a very generic message handling and serialization.
Should you feel that "|" is not to be used because conflicting with your schema you can change it with %255, but in this way you lose the notecard serialization.
Also the protocol doesn't handle the float to string problem, which under "normal" situations should not be a big problem.

If you need to have
* "|" character in your strings
* maximum precisions in float (more than 3-4 decimals)
Don't use this or adapt with proper serialization.

On the other hand the advantage are:
* very simple
* low footprint (you can even inline it)
* very fast (no complex serializations needed)

And here the basic code (you can even inline these functions but leaving it as function will allow for refactoring and ease the code understanding):

== Serialization / Deserialization ==
<pre>

string dumpList(list lst)
{
return llDumpList2String(lst,"|");
}
list parseString(string str)
{
return llParseStringKeepNulls(str,["|"],[]);
}

</pre>

When needing to send a message use the following:
<pre>

// for linkset:
llMessageLinked(LINK_SET,1,dumpList( [ sME, "TEXT", "SHOW", str, vcolor ]),"");

// for say channels:
llSay(CHANNEL,dumpList( [ sME, "TEXT", "SHOW", str, vcolor ] );
</pre>

When needing to execute the command do something like:

<pre>
link_message(integer channel,integer num, string message,key id)
{
debug("got msg "+message);
// message has the form [ from, to, cmd, parms ]
list array=parseString(message);
string src=llList2String(array,0);
string dst=llList2String(array,1);
string cmd=llToLower(llList2String(array,2));
string parm1=llList2String(array,3);
string color=llList2String(array,4);

// answers only if we are the target
if(dst!=sME) return;
</pre>

Note the use of sME for each script for rapid deciding it's me.

Each object in the linkset listening area should have unique sME global variable.

Protocol allows for broadcasting messages for special situations:

RESET!!!

for example allowed for resetting all pieces.