Aha! Thanks Ross that is clear.
My application does not require any external stimuli to cause actions within the server. It has no UI. If external stimuli were needed I would hope to be able to subclass "BasicUsageEnvironment" to achieve this without the need for periodic running of the task scheduler, but at this point I don't see a need for that. I will be doing some more testing on this with this new knowledge in mind. Many thanks for valuable help, Sid. From: live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Friday, August 17, 2012 12:52 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Do the test applications ever sleep? When I comment out the line you suggested the CPU utilization by the process does indeed go to 0%. Before you make changes I would like to know more about the use of your event triggers so that I can understand if I do need them or not. So, if you could spare a few minutes describing them I would much appreciate it. Event triggers are described in "UsageEnvironment/include/UsageEnvironment.hh". They provide a way for an external thread (i.e., outside the LIVE555 event loop) to signal an event that the LIVE555 event loop thread can handle. That's why the LIVE555 event loop has to wake up on occasion - to check whether an external thread has triggered an event (using an 'event trigger). So the question here is: Will you server ever be signaled by an external thread - e.g., by a GUI? If not, then you won't need event triggers. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
