20,741
edits
Property tree: Difference between revisions
Jump to navigation
Jump to search
→Introduction
| Line 37: | Line 37: | ||
Values in the tree are typed, but they can also be untyped strings which will be converted to a typed value when read. | Values in the tree are typed, but they can also be untyped strings which will be converted to a typed value when read. | ||
== Protocol Options == | |||
Usually the "best" way depends on your specific circumstances. Will the two applications be running on the same machine? If not, do the | |||
two machines have a high speed network connection or some slow radio modem type connection? How much data are you sending and at what | |||
rate? Do you need really tight timing or can you get by with some delays and sloppiness in the communication? | |||
== Introduction == | == Introduction == | ||
When a simulation is running, all the variables such as position, speed, flaps, cabin lights, et all are calculated and manipulated through a property tree, which is exposed through various means, inculding a built-in [[Property Tree/Web Server]] and a built-in [[Telnet usage|Telnet server]]. | When a simulation is running, all the variables such as position, speed, flaps, cabin lights, et all are calculated and manipulated through a property tree, which is exposed through various means, inculding a built-in [[Property Tree/Web Server]] and a built-in [[Telnet usage|Telnet server]]. | ||
| Line 46: | Line 50: | ||
Now there are six network interfaces running that you can access from anywhere ;-) >> can I borrow your ipod please. why ? | Now there are six network interfaces running that you can access from anywhere ;-) >> can I borrow your ipod please. why ? | ||