ace project writes: > > >> The first important decision now is, do we >> > multi-threading or multiplexing-IO ? For multiplexing, >> > PLIB can be used. For multi-threading, we got a problem. >> > Another issue is how to get the code to compile on >> > other platforms, because threading and sockets aren't >> > 100% portable, to say the least. >> >> PLIB's socket library is reasonably portable. It >> runs on every platform that FlightGear runs on. >> There are many "portable" open source threading >> libraries available, Boost.Thread, ZThread and >> CommonC++ to mention just a few. >> >> Bernie > >Another issue here is performance/stability. Threading >gives best performance(and most problems) with >multiple processors. With a single processor the >overhead might not measure up against performance. I >don't have such an archictecture so bugs might not >surface at my platform.
I think you will find that the PLib 'multiplexing' code a good 'base' in that it is patterned after a high-performance mechanism. http://www.nightmare.com/medusa/medusa.html which has 'proven' itself to be fast enough for real work even when written in Python. ie Zope http://www.zope.org Cheers Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
