Using separate RTSPClient objects - that's exacty I'm going to do. Ok, seems I have found a solution: RTSPClient class is derived from Medium class and there is Medium::name() available which returns unique value.
Alternatively, you could subclass "RTSPClient", and store your information in fields in the subclass.
I have another question. Do I need to delete RTSPClient objects myself (as well as UsageEnvironment and TaskScheduler)?
Yes, unless, of course, you will be exiting the application anyway (as "openRTSP" does when it finishes).
The openRTSP application does not show how to do this properly.
In general, you should reclaim objects in the reverse order that they were created. So, to reclaim your "RTSPClient", "UsageEnvironment" and "TashScheduler" objects, do the following (after reclaiming other objects):
Medium::close(rtspClient); env->reclaim(); delete scheduler;(Yes, this is all really ugly and inconsistent. Someday it might get improved...)
-- Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
