> Thanks Ross! I just realised it might be neater to provide forwarding
> functions in RTSPClientSession, eg:
>
> protected:
> void setRTSPResponse(RTSPServer::RTSPClientConnection*
> ourClientConnection, char const* responseStr) {
> ourClientConnection->setRTSPResponse(responseStr); }
>
What's the correct way for my derived class to write a response?
Currently the only solution I can see is to also derive from
RTSPClientConnection and add a new function that forwards to
setRTSPResponse (it's not virtual, so I can't just override it).
However it seems like setRTSPResponse() sho
> What's the correct way for my derived class to write a response? Currently
> the only solution I can see is to also derive from RTSPClientConnection and
> add a new function that forwards to setRTSPResponse (it's not virtual, so I
> can't just override it). However it seems like setRTSPRespons
Hi,
I'm following the instructions in
RTSPClientSession::handleCmd_GET_PARAMETER() in order to handle RTSP
GET_PARAMETER properly (using latest 2013.04.30).
I've derived from RTSPClientSession and reimplemented
handleCmd_GET_PARAMETER(), now I'd like to call
RTSPClientConnection::setRTSPRes
