20,741
edits
Telnet usage: Difference between revisions
Jump to navigation
Jump to search
m
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01402.html
(→subscribe and unsubscribe: some people are obviously unaware of subscribe/unsubscribe) |
m (http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01402.html) |
||
| Line 34: | Line 34: | ||
commands per line. Commands could be separated with semicolons. Or perhaps some commands could take more than one argument, eg "get /foo/bar /foo/baz"). For higher bandwidth needs, it would work better to send over an FGNetFDM structure (src/Network/net_fdm.hxx) via UDP or some other custom structure. | commands per line. Commands could be separated with semicolons. Or perhaps some commands could take more than one argument, eg "get /foo/bar /foo/baz"). For higher bandwidth needs, it would work better to send over an FGNetFDM structure (src/Network/net_fdm.hxx) via UDP or some other custom structure. | ||
TCP sockets are easier to implement for almost all applications, precicely because they are reliable. UDP will only look easier if you plan on skipping the code to recover from a lost packet. Some applications can do this, but the property tree can't -- property access is non-idempotent in the general case. Listeners can have side effects. | |||
== Telnet Server == | == Telnet Server == | ||