Talk:LSL Protocol/Restrained Love Open Relay Group/simwide
I have an alternate suggestion.
Instead of doing something like !x-simwide|@getstuff=1234, (whose answer should be listened for on a new listener on channel 1234), why not go for !x-forward/getstuff, which the relay would answer on the relay channel (or whatever mean of communication was negociated before between relay and furniture)?
Typical conversation
C -> R: outfit_query,!x-forward/getoutfit C <- R: outfit_query,!x-forward/getoutfit,110010011111
I believe my approach is more versatile (works whatever is the actual communication type) and easier to use (no need to listen to another channel).
What do you think?
- OK. There is no new listener to open for the grabber; I then add !x-sensor in a separate x-tension.
- --Dahlia Orfan 10:56, 9 June 2011 (PDT)
--Satomi Ahn 02:21, 9 June 2011 (PDT)
Of course, the choice of the actual channel between viewer and relay would be up to the relay's implementation. One could even imagine that the viewer does not use chat channels at all (have you seen the new firestorm LSL bridge? Communication from viewer to bridge uses LSL http-in capabilities instead of channel chat. If that bridge eventually included a RLV relay, it could make use of such means of communication.
Firestorm LSL bridge: [1]
--Satomi Ahn 02:25, 9 June 2011 (PDT)
I also believe !x-sensor has uses on its own and should belong to its own separate !x-tension. For !x-sensor, I suggest again that the answer should be sent on the relay channel, or whatever mean of communication previously negociated, so we don't have to open a new listener. Since we use llRegionSayTo anyway, there is no danger of overspamming the default relay channel anymore.
--Satomi Ahn 02:42, 9 June 2011 (PDT)
Here is my alternate proposal: forward.
--Satomi Ahn 04:08, 9 June 2011 (PDT)