On Fri, 28 Aug 2015, Erik Janssen wrote:

> RTSP with RTP interleaving using the multi interface only works correct with
> one session per host at a time.
>
> Each of my curl handles has a different CURLOPT_INTERLEAVEDATA. If I play
> more than one session from a single host then curl may pass the
> CURLOPT_INTERLEAVEDATA of the wrong curl handle to my
> CURLOPT_INTERLEAVEFUNCTION, which is always the same.

Can you help us with a recipe on how to repeat this problem? Preferably
something that we can even use our own test suite as it makes things so much
easier to debug and will help us avoid regressions in the future!

> Furthermore I notice that when I do curl_easy_getinfo( my_curl,
> CURLINFO_LASTSOCKET, &sock) while the RTSP session is running I always get
> -1.

That's a documented limitation though that actually goes for
curl_easy_getinfo() in general. We're discussing changing that, both the
general documented limit and allowing LASTSOCKET (ACTIVESOCKET really, as
that's the new option that will take over from now on) to return a socket
earlier or at any point probably.

> there might be a relation because both the curl_easy_getinfo-call and the
> rtsp.c make use of Curl_getconnectinfo() and that one may be confused. But
> my understanding of the internal connection- and session handling is still
> poor

You might be right. RTSP in libcurl sometimes suffer from not being used by
that many users.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html