Bugs item #3388263, was opened at 2011-08-08 12:58
Message generated for change (Settings changed) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3388263&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: RTSP
Group: wrong behaviour
>Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Tinus van den Berg (tinusvdb)
Assigned to: Daniel Stenberg (bagder)
Summary: Independant RTSP connections

Initial Comment:
Background:
Assume UDP streaming... Some RTSP servers require a dedicated RTSP connection for every streaming session. This RTSP connection must stay alive for the duration of streaming, and keep alive (OPTIONS/GET_PARAMETER) messages might be sent periodically. If the connection is closed or keep-alive has not been received ,udp streaming will be stopped.

Problem:
We make use of the multi-interface and have a curl handle per stream. When trying to start multiple streams Curl tries to re-use the connection that the first stream creates to start the other streams. The result is that the RTSP server is in an invalid state as it is being bombarded with RTSP requests from different stream requests, and the RTSP session fails for all streams.

What we tried:
We tried to set CURLOPT_FRESH_CONNECT during an OPTIONS request to try force a new connection for each stream/curl handle. The result is that curl creates 3 connections which at first seems correct, BUT, these connections are not tied to the curl handle that requested them, so the Curl multi manager basically uses whichever connection it thinks is free to be used and all hell breaks loose again. Server in wrong states etc.

Question:
Is it possible to provide way to specify that a connection that was created by a specific curl handle should only be used for that curl handle. This way we can have a Fresh connection per session, that is tied to the curl handle, and can only be used by that curl handle. We can then also use CURL_FORBID_REUSE on a Teardown request to close the connection related to a RTSP session when we want to stop streaming.

Hope this makes sense, any help would be appreciated.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2011-08-13 19:55

Message:
Thanks for your question, but it seems completely wrong position. You're
asking for guidance/features and you're not reporting a bug so a bug report
about this isn't very suitable.

I suggest you bring this topic to the curl-library mailing list where we
can discuss exactly what isn't working right now and what we can do to make
it work better for RTSP cases such as yours!

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3388263&group_id=976
Received on 2011-08-19