LSL Protocol/Restrained Love Relay/Specification - Revision history

Sei Lisa: /* Example */ Revert edit of example so it is correct

2013-12-09T13:01:41Z

Example: Revert edit of example so it is correct

← Older revision		Revision as of 06:01, 9 December 2013
Line 98:		Line 98:
	Relay : BunchoCommands,7adf6218-ab26-8566-8387-660133840794,@tplm=n,ok		Relay : BunchoCommands,7adf6218-ab26-8566-8387-660133840794,@tplm=n,ok
	Relay : BunchoCommands,7adf6218-ab26-8566-8387-660133840794,@tplure=n,ok		Relay : BunchoCommands,7adf6218-ab26-8566-8387-660133840794,@tplure=n,ok
	Relay : BunchoCommands,7adf6218-ab26-8566-8387-660133840794,@remoutfit:shoes=force,ok		Relay : BunchoCommands,7adf6218-ab26-8566-8387-660133840794,@remoutfit:shoes=force,ko

	After a relog :		After a relog :

Uzume Grigorovich: cleanup

2012-07-29T08:23:27Z

cleanup

Show changes

Batche Manen: Removed leftover !vision or !visionclear from Messages from in-world object to Relay (Formal Requirements), actual explanation of them was removed 17th April '09

2010-08-22T11:30:58Z

Removed leftover !vision or !visionclear from Messages from in-world object to Relay (Formal Requirements), actual explanation of them was removed 17th April '09

← Older revision		Revision as of 04:30, 22 August 2010
Line 118:		Line 118:
	*** ''command'' ::= <rl_command> or <metacommand>		*** ''command'' ::= <rl_command> or <metacommand>
	*** ''rl_command'' ::= '''@'''behav[''':'''option]['''='''param]		*** ''rl_command'' ::= '''@'''behav[''':'''option]['''='''param]
	*** ''metacommand'' ::= '''!version''' or '''!release''' or '''!pong''' or '''!implversion''' or '''!handover/'''<handoverparameter> ~~or '''!vision/'''<visionparameter> or '''!visionclear'''~~ or '''!who/'''<whoparameter>		*** ''metacommand'' ::= '''!version''' or '''!release''' or '''!pong''' or '''!implversion''' or '''!handover/'''<handoverparameter> or '''!who/'''<whoparameter>

	** '''''Messages from Relay to in-world object (4 tokens) :'''''		** '''''Messages from Relay to in-world object (4 tokens) :'''''

Toy Wylie: Added RestrainedLove category

2010-07-06T18:14:44Z

Added RestrainedLove category

← Older revision		Revision as of 11:14, 6 July 2010
Line 206:		Line 206:

	You can find the change history of this specification at [[LSL Protocol/Restrained Love Relay/Change History\|Change History]],		You can find the change history of this specification at [[LSL Protocol/Restrained Love Relay/Change History\|Change History]],

			[[Category:RestrainedLove]]

Marine Kelley at 17:25, 26 February 2010

2010-02-26T17:25:58Z

← Older revision		Revision as of 10:25, 26 February 2010
Line 1:		Line 1:
	{{Restrained ~~Life~~ Relay Specs TOC}}		{{Restrained Love Relay Specs TOC}}

	'''VERSION 1.100'''		'''VERSION 1.100'''
Line 9:		Line 9:
	==Audience==		==Audience==

	This document is meant for people who want to create or modify '''in-world objects''' to use the features of someone else's [http://realrestraint.blogspot.com ~~RestrainedLife~~ viewer], typically '''cages''' and '''pieces of furniture''', which per definition are usually not owned by that person.		This document is meant for people who want to create or modify '''in-world objects''' to use the features of someone else's [http://realrestraint.blogspot.com RestrainedLove viewer], typically '''cages''' and '''pieces of furniture''', which per definition are usually not owned by that person.


Line 15:		Line 15:
	==Introduction==		==Introduction==

	The [http://realrestraint.blogspot.com ~~RestrainedLife~~ viewer] only executes commands issued through [[llOwnerSay]] () messages. Therefore, in order to issue commands to someone using the viewer who does not own the object, that person must wear an attachment that '''relays''' commands after some '''security checks'''.		The [http://realrestraint.blogspot.com RestrainedLove viewer] only executes commands issued through [[llOwnerSay]] () messages. Therefore, in order to issue commands to someone using the viewer who does not own the object, that person must wear an attachment that '''relays''' commands after some '''security checks'''.


Line 68:		Line 68:
	Couldn't you write it yourself and publish it?		Couldn't you write it yourself and publish it?

	Of course I could, and there is even a working code for a basic relay at [[LSL Protocol/Restrained ~~Life~~ Relay/Reference Implementation\|Reference Implementation]]. However:		Of course I could, and there is even a working code for a basic relay at [[LSL Protocol/Restrained Love Relay/Reference Implementation\|Reference Implementation]]. However:
	* The protocol is likely to improve because nobody sees the future		* The protocol is likely to improve because nobody sees the future
	* One object only would not suit everyone's needs		* One object only would not suit everyone's needs
Line 109:		Line 109:
	===Common requirements to the Relay and the in-world object===		===Common requirements to the Relay and the in-world object===

	* The chat channel used by both the Relay and the in-world object is '''-1812221819'''. That's "RLVRS" ("~~RestrainedLife~~ Viewer Relay Script") translated from alphabet to numbers.		* The chat channel used by both the Relay and the in-world object is '''-1812221819'''. That's "RLVRS" ("RestrainedLove Viewer Relay Script") translated from alphabet to numbers.

	* Messages on the channel are described here in a pseudo [http://en.wikipedia.org/wiki/Backus-Naur_form Backus-Naur Form] :		* Messages on the channel are described here in a pseudo [http://en.wikipedia.org/wiki/Backus-Naur_form Backus-Naur Form] :
Line 205:		Line 205:
	== History ==		== History ==

	You can find the change history of this specification at [[LSL Protocol/Restrained ~~Life~~ Relay/Change History\|Change History]],		You can find the change history of this specification at [[LSL Protocol/Restrained Love Relay/Change History\|Change History]],

Marine Kelley: moved LSL Protocol/Restrained Living Relay/Specification to LSL Protocol/Restrained Love Relay/Specification

2010-02-26T17:24:26Z

moved LSL Protocol/Restrained Living Relay/Specification to LSL Protocol/Restrained Love Relay/Specification

← Older revision	Revision as of 10:24, 26 February 2010
(No difference)

Marine Kelley: moved LSL Protocol/Restrained Life Relay/Specification to LSL Protocol/Restrained Living Relay/Specification

2010-02-25T19:20:06Z

moved LSL Protocol/Restrained Life Relay/Specification to LSL Protocol/Restrained Living Relay/Specification

← Older revision	Revision as of 12:20, 25 February 2010
(No difference)

Marine Kelley: /* Deprecated metacommands */

2009-06-06T16:23:25Z

Deprecated metacommands

← Older revision		Revision as of 09:23, 6 June 2009
Line 163:		Line 163:

	===Deprecated metacommands===		===Deprecated metacommands===
	The following metacommands used to belong to the specification ~~without~~ without much discussion and without permission. They are mentioned here for reference but never meant to be part of the specification. They might be reinstated one day if they prove themselves useful, but at the time of this writing it would make no sense to consider a relay to be out of spec if it didn't implement those metacommands.		The following metacommands used to belong to the specification without much discussion and without permission. They are mentioned here for reference but never meant to be part of the specification. They might be reinstated one day if they prove themselves useful, but at the time of this writing it would make no sense to consider a relay to be out of spec if it didn't implement those metacommands.

	====="!who" metacommand=====		====="!who" metacommand=====

Marine Kelley at 16:18, 6 June 2009

2009-06-06T16:18:43Z

← Older revision		Revision as of 09:18, 6 June 2009
Line 1:		Line 1:
	{{Restrained Life Relay Specs TOC}}		{{Restrained Life Relay Specs TOC}}

	'''VERSION 1.~~050~~'''		'''VERSION 1.100'''

	Written and maintained by {{User\|Marine Kelley}}.		Written and maintained by {{User\|Marine Kelley}}.

Marine Kelley: /* Deprecated metacommands */

2009-06-06T16:09:24Z

Deprecated metacommands

← Older revision		Revision as of 09:09, 6 June 2009
Line 163:		Line 163:

	===Deprecated metacommands===		===Deprecated metacommands===
	The following metacommands used to belong to the specification without without much discussion and without permission. They are mentioned here for reference but ~~are not~~ part of the specification. They might be reinstated one day, if they prove themselves useful but at the time of this writing, it would make no sense to consider a relay to be out of spec if it didn't implement those metacommands.		The following metacommands used to belong to the specification without without much discussion and without permission. They are mentioned here for reference but never meant to be part of the specification. They might be reinstated one day if they prove themselves useful, but at the time of this writing it would make no sense to consider a relay to be out of spec if it didn't implement those metacommands.

	===="!who" metacommand====		====="!who" metacommand=====
	* Syntax: !who/<uuid>		* Syntax: !who/<uuid>
	* This is an information message from the world telling the relay which avatar is controlling it.		* This is an information message from the world telling the relay which avatar is controlling it.
Line 173:		Line 173:
	''Note from Marine : This metacommand may be designed to check the avatar operating the object to make griefing harder... but if this command is only as trustworthy as the object is, I don't see that as an improvement security-wise. Otherwise the idea has merit.''		''Note from Marine : This metacommand may be designed to check the avatar operating the object to make griefing harder... but if this command is only as trustworthy as the object is, I don't see that as an improvement security-wise. Otherwise the idea has merit.''

	===="!handover" metacommand====		====="!handover" metacommand=====
	* Syntax: !handover/<key>/<type>		* Syntax: !handover/<key>/<type>
	* Allows one world object to tell the relay it should accept commands from another world object instead without asking for permissions again. (For example a kidnapper object may do a force tpto to another sim where an other world object is waiting for the victim.		* Allows one world object to tell the relay it should accept commands from another world object instead without asking for permissions again. (For example a kidnapper object may do a force tpto to another sim where an other world object is waiting for the victim.
Line 183:		Line 183:
	* The relay must ensure with the !ping meachnism that the target object is available.		* The relay must ensure with the !ping meachnism that the target object is available.
	* The target object, however, might not be able to see the ping: For example because of a slow intersim teleport. In this case the target object must send a !pong on arrival of the victim anyway.		* The target object, however, might not be able to see the ping: For example because of a slow intersim teleport. In this case the target object must send a !pong on arrival of the victim anyway.
	''Note from Marine : This metacommand is particularly interesting, and is likely to go to the Other Metacommands section, or even in the main spec. It needs to be designed thoroughly first, though. I don't think it needs to be so complex, but it sure needs some checking.''		''Note from Marine : This metacommand is particularly interesting, and is likely to go to the Other Metacommands section in the future, or even in the main spec. It needs to be designed thoroughly first, though. I don't think it needs to be so complex, but it sure needs some checking.''

	===Relay requirements===		===Relay requirements===