Difference between revisions of "LSL Protocol/Restrained Love Open Relay Group/listen"
Satomi Ahn (talk | contribs) (New page: =!x-listen= !x-listen/xxxx: changes the communication beween relay and controlling device to channel xxxx instead of RLVR, assuming xxxx is a high negative integer. Motivation: the relay ...) |
Satomi Ahn (talk | contribs) |
||
| Line 21: | Line 21: | ||
(session on channel RLVR between R and C) | (session on channel RLVR between R and C) | ||
-RLVR> blah,k(R),@randomlockingcommand=n|!x-listen/-12345 | -RLVR> blah,k(R),@randomlockingcommand=n|!x-listen/-12345 | ||
<RLVR- blah,k(C),@randomlockingcommand=n,ok | |||
<RLVR- blah,k(C),!x-listen/-12345,ok | <RLVR- blah,k(C),!x-listen/-12345,ok | ||
(session continues on channel -12345) | (session continues on channel -12345) | ||
It is not recommended to place other commands after the !x-listen, as it is not clear on which channel they should be acknowledged (depending on whether or not the relay ok's the !x-listen, and even when ok'd it is might make relay implementation harder in some cases if the acknowledgement channel changes within a batch of commands). | It is not recommended to place other commands after the !x-listen, as it is not clear on which channel they should be acknowledged (depending on whether or not the relay ok's the !x-listen, and even when ok'd it is might make relay implementation harder in some cases if the acknowledgement channel changes within a batch of commands). | ||
Revision as of 06:09, 2 June 2009
!x-listen
!x-listen/xxxx: changes the communication beween relay and controlling device to channel xxxx instead of RLVR, assuming xxxx is a high negative integer.
Motivation: the relay and the device thus stop spamming the RLVR channel with messages that only concerns those two objects.
Scenario:
(session on channel RLVR between R and C) -RLVR> blah,k(R),!x-listen/-12345 <RLVR- blah,k(C),!x-listen/-12345,ok (session continues on channel -12345)
Neither R and C are required to listen on channel RLVR after this. It is even recommended that R and C close every useless listener.
Both R and C are required to listen to each other on channel -12345 after this dialog.
C should only propose high negative channels (<1000). The relay is not required to accept any other channel than high negative ones. If the proposed channel is wrong, the relay can "ko" the message.
Recommendation: this command should preferably be used after the session is locked, as the relay is not required to retain any data concerning a non-locking device.
Good practice scenario:
(session on channel RLVR between R and C) -RLVR> blah,k(R),@randomlockingcommand=n|!x-listen/-12345 <RLVR- blah,k(C),@randomlockingcommand=n,ok <RLVR- blah,k(C),!x-listen/-12345,ok (session continues on channel -12345)
It is not recommended to place other commands after the !x-listen, as it is not clear on which channel they should be acknowledged (depending on whether or not the relay ok's the !x-listen, and even when ok'd it is might make relay implementation harder in some cases if the acknowledgement channel changes within a batch of commands).