[Live-devel] Proper way to terminate client

Bob Koninckx bob.koninckx at gmail.com
Mon Sep 24 04:09:55 PDT 2007


mmm... I am not sure if I like this approach. In our aplication, there
may be more than one incoming stream (thus more than one
MultiFramedRTPSource, all attached to the same environment ad
scheduler). What I want to accomplish is to remove one of these, without
the others noticing, hence, without stopping the event loop.

Thanks for your suggestion though,

Bob


On Mon, 2007-09-24 at 12:47 +0200, Ramon Martin de Pozuelo Genis wrote:
> Hi Bob,
> you may use a watchVariable in the doEventLoop like this
>     ...
>         watchVariable=0;
>         env->taskScheduler().doEventLoop(&watchVariable);
>    ...
> and add a socket or a new thread that permits you to change this variable
> externally. When the Scheduler watch this variable is modified it will go out
> from the EvenLoop, and then, if you want you could stop what you want or call
> again doEventLoop(&watchVariable);
> 
> It is the form that I use it. I hope this helps you.
> 
> Ramon
> 
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel



More information about the live-devel mailing list