David Megginson <[EMAIL PROTECTED]> wrote: > Here's my suggestion: forget about the internal environment manager (disable > it, if possible) and for now, manage the weather entirely though an external > daemon written in Perl, Python, Java, C, C++, PHP, or what-have-you.
On the one hand it's nice not to have FlightGear functionality scattered over dozends of processes ;-) but especially in the current case the idea of an external program comes handy: Those who run FlightGear on a system behind a firewall could profit from an exernal 'subsystem' because they could run it on the firewall itself, eliminating the need for workarounds to run over some HTTP proxy, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
