]> git.mxchange.org Git - flightgear.git/commit
Investigating some wierd behavior where the threaded metar fetcher would
authorcurt <curt>
Sat, 28 Feb 2004 19:52:17 +0000 (19:52 +0000)
committercurt <curt>
Sat, 28 Feb 2004 19:52:17 +0000 (19:52 +0000)
commitd8000569eabff436d5452f84b40ca88ecd8f0cdd
tree0a10643a3b6ff0aa3b4326096d9b97b07de47f36
parentfeb9f16410cd4c4aae459f99b6caacd91e283d17
Investigating some wierd behavior where the threaded metar fetcher would
occasionally cause a large number of valid stations to be flagged as invalid.
This *seemed* like a "race condition" type problem because there were some
assumptions in the communication between the main process and the threaded
loader which if they broke down could lead to this problem.

In the process of removing this ambiguity, I restructured the threaded
(and non-threaded) metar fetching code a bit.  Some of the top level logic
(which Erik politely left untouched) didn't make nearly as much sense in the
context of a threaded metar loader and could have contributed to some of the
wierdness I was seeing.
src/Environment/environment_ctrl.cxx
src/Environment/environment_ctrl.hxx