> OK, so the “addNewStream” triggered event, where the RTSPClient is created,
> would add the pointer to it then. I’m a bit concerned about thread-safety
> here, since the struct is created on the GUI thread, then manipulated on the
> live555 thread. I suppose you’re implying that safety would c
> On Nov 12, 2014, at 12:31 PM, Ross Finlayson wrote:
>
>> I’ve got this working along the lines you’ve described, but the problem I’m
>> running into is a need for some kind of external (to live555 thread)
>> reference to each RTSPClient, in order to trigger other events (stopping
>> one, fo
> I’ve got this working along the lines you’ve described, but the problem I’m
> running into is a need for some kind of external (to live555 thread)
> reference to each RTSPClient, in order to trigger other events (stopping one,
> for example). That’s why I thought about creating the clients out
Hi Ross,
Thanks for your help so far.
I’ve got this working along the lines you’ve described, but the problem I’m
running into is a need for some kind of external (to live555 thread) reference
to each RTSPClient, in order to trigger other events (stopping one, for
example). That’s why I though
First you need to figure out exactly when/how you’re going to decide when to
add a new stream. I.e., you need to figure out what event will cause this to
happen.
If it’s simply a delayed task - within the event loop (i.e., set up using
“TaskScheduler::scheduleDelayedTask()”) - then you don’t n
>
>> With a single event loop, how does one add new client requests to the
>> already running loop?
>
> You can create new “RTSPClient” objects and call operations on them
> (including “sendDescribeCommand()”) from within the event loop, at any time.
> I.e., this could be done from code that’
> Our client app needs to receive multiple streams at once, adding them as
> required by various parts of the application logic.
>
> Both playCommon.cpp and testRTSPClient.cpp appear to require any
> client->sendDescribeCommand() calls before the env->scheduler().doEventLoop()
> call.
No - alt
Hello,
Our client app needs to receive multiple streams at once, adding them as
required by various parts of the application logic.
Both playCommon.cpp and testRTSPClient.cpp appear to require any
client->sendDescribeCommand() calls before the env->scheduler().doEventLoop()
call. With a single
