[... Paul Morriss wrote ...] > My proposal solution to the above questions are that > we use "shared memory" or ethernet communications > (user selectable), the main flight-gear app will not > really contain the AI code, it will be done by the > server, which updates lat, long, altitude, heading > etc, this is sent to flight-gear that then does the > displaying, sounds etc.
> The server (dynamic scenario) could then be used to > manage plane routes, knowledge bases for the flight > dynamics etc. This would support the idea of a general interface abstaction between FDM on one and the whole I/O stuff (keyboard, mouse, joystick, sound, screen) on the other end. This might fit for different purposes: 1.) Exchangeable FDM on local machine 2.) remote FDM with 'stupid' front-end 3.) multiplayer-server 4.) AI ... Paul's idea resembles me of the way X clients communicate with the server. Local clients prefer shared memory (at least on several commercial Unices, I believe it's the same on XFree86), remote clients use TCP/IP. I don't know how portable this could be .... ? 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
