Am I understood correctly: client session object deleted in
multicast mode, even one client from multi has a timeout
Yes, but note that the "RTSPClientSession" object is specific to that
particular client (and it's TCP RTSP connection to the server). If
that times out, then only that one
Mr. Ross,
Thank you very much for quick answer.
Am I understood correctly: client session object deleted in multicast mode,
even one client from multi has a timeout
ThanX again.
On Sun, Mar 6, 2011 at 12:33 PM, Ross Finlayson wrote:
> why multicast checking removed from livenessTimeoutTask A
why multicast checking removed from livenessTimeoutTask API???
Because there was no longer any need to exclude multicast sessions
from the normal client liveness checking.
I.e., as with all RTSP/RTP streams, the server will timeout the
stream if it doesn't receive any indication of 'liveness
Dear Sir!
I upgrade my old version of live555 on one latest (from 2011/Jan/24) and pay
attention on small difference in functionality in RTSP server that I don't
clearly understood. I mean this API:
void RTSPServer::RTSPClientSession
::livenessTimeoutTask(RTSPClientSession* clientSession);
As wri
