Thanks for the quick and detailed reply Ross.
My apologies you're correct it is the front-end connection we are dropping with
clumsy not the back-end as I originally stated.
I had a feeling there'd have been a good reason the live555 server was working
this way, so thanks again for the clarific
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
