160
edits
FlightGear Newsletter April 2021: Difference between revisions
Jump to navigation
Jump to search
Change of mind on changed property distribution scheme.
(Change of mind on changed property distribution scheme.) |
|||
| Line 42: | Line 42: | ||
Successive requests now can use the index to access the property removing the need to send the full property path every request saving both | Successive requests now can use the index to access the property removing the need to send the full property path every request saving both | ||
bandwidth and lookup time. | bandwidth and lookup time. After thinking about this a bit more I think future revision will have a different scheme. | ||
1. Request the id of the property you are interested in. | |||
2. You get an answer with the property value and id for that property. | |||
3. From now on the server pushes an updated value for that particular | |||
property id when the property value changes. | |||
When set up properly DDS will keep the changed properties in it's cache for clients to read whey they have time for it. | |||
So no need to do successive requests anymore. Just wait and watch out for updates. | |||
As an example, there is the fg_dds_prop utility in {{Flightgear source|src/Network/DDS/fg_dds_prop.cpp}} which can be used to either request a property path or a know property property ID. | As an example, there is the fg_dds_prop utility in {{Flightgear source|src/Network/DDS/fg_dds_prop.cpp}} which can be used to either request a property path or a know property property ID. | ||