Ross Finlayson writes:
How were you intending to use the "client data" value?
Since my application has a number of concurrent RTSP sessions, I
need to be able to tie responses back to their context. Without
a user data pointer, I can think of two options. The first is to
keep a global map
Ross Finlayson writes:
>
> How were you intending to use the "client data" value?
Since my application has a number of concurrent RTSP sessions, I
need to be able to tie responses back to their context. Without
a user data pointer, I can think of two options. The first is to
keep a global map
I tried reworking some of my code today to use the new
asynchronous interface, but ran into a couple problems. First, I
do not see a way to set the URL.
The URL is now passed as a parameter to "RTSPClient::createNew()".
This makes more sense than (the previous behavior of) passing it as a
par
Ross Finlayson writes:
>
> I have installed a new version (2010.05.29) of the "LIVE555
> Streaming Media" code that adds the long-promised new
> 'asynchronous' (i.e., non-blocking) interface to the
> "RTSPClient" class.
Thank you for publishing this new interface; I've been looking
forward to it
RTSPClient:
==
I have installed a new version (2010.05.29) of the "LIVE555 Streaming
Media" code that adds the long-promised new 'asynchronous' (i.e.,
non-blocking) interface to the "RTSPClient" class.
Each operation that sends a RTSP command now takes a 'response
handler' function as
