20,741
edits
Telnet usage: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→Use Case: Radio Stack: http://www.mail-archive.com/flightgear-devel@flightgear.org/msg06862.html) |
No edit summary |
||
| Line 26: | Line 26: | ||
In comparison to the binary native protocol, the props/telnet protocol is a lower bandwidth, high reliablity channel. You are guaranteed that every message gets to the reciever once (and only once.) This is great for setting up weather conditions, time of day, camera parameters, and anything else that might have an impact on the visuals. We have a convenient "telnet" interface to all the internal properties and built in commands. Anything you can set from the keyboard, or mouse, or gui, you can do from a remote program or script. It's much lower bandwidth, but very convenient. | In comparison to the binary native protocol, the props/telnet protocol is a lower bandwidth, high reliablity channel. You are guaranteed that every message gets to the reciever once (and only once.) This is great for setting up weather conditions, time of day, camera parameters, and anything else that might have an impact on the visuals. We have a convenient "telnet" interface to all the internal properties and built in commands. Anything you can set from the keyboard, or mouse, or gui, you can do from a remote program or script. It's much lower bandwidth, but very convenient. | ||
The telnet mechanism is not designed to be high bandwidth. I believe it runs at 5hz? and only processes one line/command per iteration. | |||
It would work better to send over an FGNetFDM structure | |||
(src/Network/net_fdm.hxx) via UDP. | |||
== Telnet Server == | == Telnet Server == | ||