> ps. Are you related at all to Yuri Gagarin (the world’s most
> famous “Gagarin” :-)? (Or is “Gagarin” a common name in Russia?)
Hi Ross
No, I'm not related to Yuri Gagarin :)
This family is common enough.
___
live-devel mailing list
live-devel@li
> On Aug 28, 2019, at 8:12 PM, Sergei Gagarin wrote:
>
> Or modify RTSPClient::sendGetParameterCommand (file RTSPClient.cpp)
> to ignore zero length parameter names.
I decided to do this (because the previous behavior - sending “\r\n” as content
- was not really meaningful).
I’ve just instal
Proxy server can use GET_PARAMETER command with empty parameter
name as session liveness command.
In function ProxyRTSPClient::sendLivenessCommand (file
ProxyServerMediaSession.cpp)
we see this code:
rtspClient->sendGetParameterCommand(*sess, ::continueAfterGET_PARAMETER, "",
rtspClient->auth())
> I just started with live555 media server and my client starts with
> GET_PARAMETER method rather than OPTIONS.
> After reading RTSPServer.cpp i found that the method GET_PARAMETER is
> implemented just as a 'keep alive' and it sends an empty response.
Does the server send back an empty "200 OK
Hello,
I just started with live555 media server and my client starts with
GET_PARAMETER method rather than OPTIONS.
After reading RTSPServer.cpp i found that the method GET_PARAMETER is
implemented just as a 'keep alive' and it sends an empty response.
i understand that i must define a subclass o
I read that openRTSP can send GET_PARAMETER as keepAlive (or client
liveness indicator) but nothing in the source code show that (in
RTSPClient.cpp).
Not true. The "RTSPClient" class supports sending the
"GET_PARAMETER" command, using the "getMediaSessionParameter()"
member function. (Howev
Hello,
I read that openRTSP can send GET_PARAMETER as keepAlive (or client liveness
indicator) but nothing in the source code show that (in RTSPClient.cpp).
During our session, the timeout is sent by the video server in the RTSP
SETUP response and catched by openRTSP, but nothing append then when
