Paul Morriss writes: > I have created a "portable" ethernet library that > supports both Linux and Windows, this would give us > total portability, although you would have to watch > out for big-endian conversion between Linux and > Window.
Just so you know, plib also has a portable network library that works across, linux, windows, macos, sgi, etc. We have been using that with good success for many aspects of the FlightGear project. > The second reason I am in support of an "external" server is that ai > can start to eat processing time, specially if you have lots of > stuff going on, where as if you are just sending an update message > across the network you are keeping the logic out of the main code > base. I think this makes a lot of sense. > Also as Martin pointed out, this would also aid multi > player support, as several flight-gear users can talk > to the same scenario, thus they can fly around > in unison. > > Ohh and I am in total support of well defined interface ;) (As long as I get to define it.) :-) :-) Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
