> On Dec 15, 2020, at 9:21 PM, Lionel Koenig wrote:
>
> I just wanted to clarify the use case here: In our application, the end user
> decides when to SETUP and PLAY the stream which is presented to her/him after
> the DESCRIBE succeeded. It is also the end user deciding whenever to TEARDOWN
Hi Ross,
I completely understand your position.
I just wanted to clarify the use case here: In our application, the end
user decides when to SETUP and PLAY the stream which is presented to
her/him after the DESCRIBE succeeded. It is also the end user deciding
whenever to TEARDOWN the stream. Usuall
OK, so let me get this straight: You are doing something (calling LIVE555 code
(beyond just “triggerEvent()”) from a thread outside the event loop) that you
know is ‘unsupported’, and which you (should) also know could produce many race
conditions that may cause your application to fail in unpre
When sending RTSP command from another thread than the event loop (it is
actually unsupported see:
http://www.live555.com/liveMedia/faq.html#threads), the response of the
command might arrive prior the handler callback is registered. When that
happen, the handler will never be called even if the re
