Another question about callbacks.
Is it ok to pass a NULL callback if we don't care about the response ?
It seems to be ok, and it seems to be checked in your code, but as it is
not explicitly authorized in your functions descriptions
(RTSPClient.hh), I wanted to be sure it is supported.
Yes, th
Hi Ross,
Another question about callbacks.
Is it ok to pass a NULL callback if we don't care about the response ?
It seems to be ok, and it seems to be checked in your code, but as it is
not explicitly authorized in your functions descriptions
(RTSPClient.hh), I wanted to be sure it is supported.
Selon Ross Finlayson :
> Do you plan to have more than one "RTSPClient" object concurrently?
> If not, then you can just use a global variable. But if you do plan
> to have more than one "RTSPClient" object concurrently, then you can
> define a subclass, and add your 'application data' there.
Y
I am trying to adapt vlc to the live555 asynchronous API
That's great - thanks!
, and I have a
question.
Callbacks functions declaration is :
typedef void (responseHandler)(RTSPClient* rtspClient, int resultCode,
char* resultString);
But how can I access my application data in this callback.
Hi,
I am trying to adapt vlc to the live555 asynchronous API, and I have a
question.
Callbacks functions declaration is :
typedef void (responseHandler)(RTSPClient* rtspClient, int resultCode,
char* resultString);
But how can I access my application data in this callback.
Why the callback paramat
