I went back to my thread model. I am afraid threads are already in existence and reworking everything at the moment is not possible.
It is running great on rtsp, my custom push-rtsp and my http->restreamer. I think I have accumulated enough knowledge to write a multistream version of openRTSP. :) Would that be a good testProg ?? From: [email protected] [mailto:[email protected]] On Behalf Of Ross Finlayson Sent: Wednesday, November 30, 2011 3:40 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] problems moving to asynchronous rtsp interface 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/ ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2012.0.1873 / Virus Database: 2102/4648 - Release Date: 11/30/11
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
