>> This is my scenario:
>> Create a new ProxyServerMediaSession - it in turn calls
>> DESCRIBE on the backend.
>> Call RTSPServer::removeMediaSession or
>> RTSPServer::deleteMediaSession before that DESCRIBE call completes. (the
>> ProxySMS instance is deleted but
> What is the best way to rewrite the code so it will cleanup any open backend
> connections and handlers or protect against this scenario?
That's for me to worry about; not you :-)
> This is my scenario:
> Create a new ProxyServerMediaSession - it in turn calls
> DESCRIBE on t
Hi,
I know that the application is event based and single threaded but there is a
problem which creating a ProxyServerMediaSession and trying to delete it before
we get the describe response.
This is my scenario:
Create a new ProxyServerMediaSession - it in turn calls
DESCRIBE
