config:remotecontrol:tcp
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
config:remotecontrol:tcp [2016/09/06 15:15] – [TCP Server] tw | config:remotecontrol:tcp [2019/07/09 16:18] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 27: | Line 27: | ||
===== TCP Client ===== | ===== TCP Client ===== | ||
+ | The TCP Client remote will connect to a server via TCP/IP, and execute any remote control commands received. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In the configuration, | ||
+ | |||
+ | If a password is specified, the TCP Client will authenticate itself as soon as the connection is established: | ||
+ | |||
+ | AUTH mysecretpassword | ||
+ | | ||
+ | The authentication mechanism is designed to be compatible with one of the TCP Server remote (see above), although the current version does not allow any interaction through scripts or so. This is planned for a future release. | ||
+ | |||
+ | Similar to the TCP Server remote, you can specify a command prefix, which will filter out any commands not matching the prefix (and strip the prefix from those commands that match): | ||
+ | |||
+ | PLAYOUT1 PLAYER 1-1 START | ||
+ | | ||
+ | The command prefix is very useful when multiple clients connect to the same server. |
config/remotecontrol/tcp.1473174913.txt.gz · Last modified: 2019/07/09 16:18 (external edit)