[Live-devel] Warning: The old 'synchronous' "RTSPClient" interface will be removed, starting on June 1st, 2013

PROMONET Michel michel.promonet at thalesgroup.com
Wed Apr 24 01:25:32 PDT 2013


                Hi Ross,

Thanks for your great support.

May I suggest that probably lots of live555 users need to do the same stuff in order to send DESCRIBE,SETUP,PLAY overriding the RTSPClient to get reference to the session.
But no problem I could adapt to the available API.

Regards,

                Michel.

[@@ THALES GROUP INTERNAL @@]

De : live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] De la part de Ross Finlayson
Envoyé : mardi 23 avril 2013 17:14
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] Warning: The old 'synchronous' "RTSPClient" interface will be removed, starting on June 1st, 2013

Could it be possible from the RTSP callback to get back the context of the RTSPClient owner ?

I'm not sure what exactly you mean by 'context of the RTSPClient owner', but - after 3 years now of people using the current "RTSPClient" API - I'm certainly not going to be making any unnecessary changes to it.  You can get all the information you want from the "RTSPClient" object (perhaps by subclassing, if necessary, as you noted).

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130424/9d68a39d/attachment-0001.html>


More information about the live-devel mailing list