On Sun, 9 Nov 2003, John Barrett wrote: > Though actually -- a single master server could handle all the position > updates without that much trouble given the update limiter code and headless > (no opengl display) operation -- offload the airport and regional ATC to > stand alone apps that interface to the master server as clients. (thats > going to take some work on the ATC system to make it interface to the system > like a network peer, even for single user operation, such that you can > startup instances of the ATC code for specific airports and RATC)
Presumably you could just have a client config which specified the area of interest, and have the server send out only arcraft within that - obviously this imposes a higher load on the server though - maybe it'd be possible to do a very coarse cull on the main server, and output data to regional machines - if the protocols are consistent throughout then you'd end up with a scalable system which should (in theory) be able to cope with an awful lot of aircraft, controllers, etc etc. As the system expanded then more "localised" features could be implemented further down the chain. -- Jon Stockill [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
