Difference between revisions of "LSL Protocol/Restrained Life Relay/delay"
Jump to navigation
Jump to search
Satomi Ahn (talk | contribs) (Initial draft) |
Satomi Ahn (talk | contribs) m |
||
Line 11: | Line 11: | ||
; Description : meta command to pass a delay (in seconds) the relay has to wait before executing subsequent commands from the device. | ; Description : meta command to pass a delay (in seconds) the relay has to wait before executing subsequent commands from the device. | ||
; Background : Most of world objects just lock you in on some fixed piece of furniture, and thus can easily ensure you will eventually be released of every restriction, as it will do it at the time you are allowed to stand up. Other devices have other ways to ensure you're eventually released: for instance, zone | ; Background : Most of world objects just lock you in on some fixed piece of furniture, and thus can easily ensure you will eventually be released of every restriction, as it will do it at the time you are allowed to stand up. Other devices have other ways to ensure you're eventually released: for instance, zone controllers use a sensor and send a "!release" as soon as you exit the sensed zone. | ||
: In both case, the device is still nearby from the beginning to the end. What about if you want to restrict someone in some way, but don't want to prevent them from leaving? It is currently impossible to do it while ensuring a timely release (or you have to rely on the fact that the relay verifies the device is still nearby and active). | : In both case, the device is still nearby from the beginning to the end. What about if you want to restrict someone in some way, but don't want to prevent them from leaving? It is currently impossible to do it while ensuring a timely release (or you have to rely on the fact that the relay verifies the device is still nearby and active). | ||
: Here I propose to add another way to ensure the release of restrictions, by delaying of some fixed time the execution of a bunch of relay commands (hopefully including a !release). | : Here I propose to add another way to ensure the release of restrictions, by delaying of some fixed time the execution of a bunch of relay commands (hopefully including a !release). |
Revision as of 09:21, 21 March 2009
This is a discussion page for adding support of delays in the execution of relay commands.
!delay
Not implemeted yet
- Description
- meta command to pass a delay (in seconds) the relay has to wait before executing subsequent commands from the device.
- Background
- Most of world objects just lock you in on some fixed piece of furniture, and thus can easily ensure you will eventually be released of every restriction, as it will do it at the time you are allowed to stand up. Other devices have other ways to ensure you're eventually released: for instance, zone controllers use a sensor and send a "!release" as soon as you exit the sensed zone.
- In both case, the device is still nearby from the beginning to the end. What about if you want to restrict someone in some way, but don't want to prevent them from leaving? It is currently impossible to do it while ensuring a timely release (or you have to rely on the fact that the relay verifies the device is still nearby and active).
- Here I propose to add another way to ensure the release of restrictions, by delaying of some fixed time the execution of a bunch of relay commands (hopefully including a !release).
- Syntax
- !delay/(integer)
- (integer) is the amount of time, in seconds, you have to wait before executing subsequent commands.
- Other parameters after a second "/" should be ignored, as they could be used for a future extension.
- Discussion
- I still don't know if !delay should be applied on every subsequent command from the device, or only the ones of the bench of commands the !delay belongs to, thus allowing to affect the target while some commands are still pending.--Satomi Ahn 17:20, 21 March 2009 (UTC)