20,741
edits
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{PropertyTree}} | {{PropertyTree}} | ||
{{Note|This feature received significant updates in FlightGear 3.1+: | |||
While working on the new radio/atis implementation, Torsten rediscovered the internal httpd (aka webserver) to browse the property tree. | |||
It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal | |||
property browser and navigate to the locations after each sim restart. | |||
After a while, Torsten got disappointed by the functionality and the look&feel of the http property-browser, so he had a look at the code to see if it | |||
could be improved, he quickly realized, that the implementation was simple but not scalable, so he looked for something allready available on | |||
the GPL market. | |||
And he found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embedd that into FlightGear. | |||
What is ready so far and pushed to next is: | |||
* A single threaded httpd running in the main loop (should probably get its own thread soon) | |||
* Running as a replacement for the old httpd | |||
* Serving FGDATA/Docs as the document root | |||
* Serving the uri /props/ as a replacement for the old property browser (improved functionality, improved l&f, styling via css) | |||
* Serving the uri /run.cgi as a replacement for the old interface to run fg_commands | |||
* Serving the uri /json/ to return selected properties as JSON (read-only so far) | |||
}} | |||
[[FlightGear]] has a few network access protocols. These are started via a [[Command Line Parameters|command line option]]. | [[FlightGear]] has a few network access protocols. These are started via a [[Command Line Parameters|command line option]]. | ||