David Megginson wrote: > information available at a single glance. The alternative is to use > the multi-process model rather than a multi-thread model, and to swap > entire property trees in and out like memory pages; we'll certainly > avoid a lot of bugs that way (because the wrong properties simply > won't be available). > > What does everyone else think?
In projects like these I like to think multi-process could simplify things quite a bit. But I'v seen that perfomance wise it is sometimes better to use some kind of threading (pthread/state-thread). E.g. look at Apache (fortunately FlightGear is nowhere near the socket demands of Apache :-) ). Erik _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
