> So it seems clear that having one environment with a single scheduler the > prefered method. The side effect is of course that things printed to the env > get all jumbled up. (Windows console is over 100 times slower than a *nix > one) I can protect these with a mutex, but should we consider internally > protecting the environment streaming calls?
Remember that the various "operator<<" functions defined on a "UsageEnvironment" are pure virtual functions, and can defined to do whatever you want in a subclass. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
