20,741
edits
Recommended Property Tree Enhancements: Difference between revisions
Recommended Property Tree Enhancements (view source)
Revision as of 16:15, 26 January 2016
, 26 January 2016→Introducing "Managed Properties"
m (→Permission handling related: https://gitorious.org/fg/flightgear/commit/771586854b84f6824112f10f854488979e960094) |
|||
| Line 81: | Line 81: | ||
== Introducing "Managed Properties" == | == Introducing "Managed Properties" == | ||
{{FGCquote | |||
|1= Making the property tree thread-safe is an interesting but a very daunting task since properties are (ab)used in so many ways.. :) I have a soft spot for using multi-buffering to support concurrent readers with concurrent writers, but for something as unstructured (in terms of who writes where) as this I'm at a loss to see how or if it could be applied. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34797127/ | |||
| title = <nowiki>Re: [Flightgear-devel] Designing a thread-safe property tree API | |||
(was Re: A FGPythonSys implementation: ...)</nowiki> | |||
| author = <nowiki>Anders Gidenstam</nowiki> | |||
| date = Jan 26th, 2016 | |||
| added = Jan 26th, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
The idea is to introduce so called "managed properties" for crucial runtime state, in order to optionally ensure, enforce and maintain integrity of such state variables by using additional meta information to apply data-integrity requirements, as well as access privileges to prevent important runtime state from being mutated by non-authorized components or invalid data. | The idea is to introduce so called "managed properties" for crucial runtime state, in order to optionally ensure, enforce and maintain integrity of such state variables by using additional meta information to apply data-integrity requirements, as well as access privileges to prevent important runtime state from being mutated by non-authorized components or invalid data. | ||