Mark,
There are two huge problems with this. First,
“ClientSession::livenessTimeoutTask()” is usually called when a client happens
to go away without sending a RTSP “TEARDOWN” command. But other clients might
continue to be (concurrently) accessing the server (in this case, a proxy
server) O
Hello,
When running the ProxyServer application from the live555 testProgs on windows
I have encountered an issue where sockets are not released when a client
session is timed out.
Put some logging around the select call in BasicTaskScheduler to output the
read, write and except socket counts