With this in mind I was wondering if Medium::close(rtspClient) is
enough to reclaim RTSPClient objects? It seems this function doesn't
release object's memory.
Yes it does (see "Media.cpp", line 175).
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
er 03, 2010 4:24 PM
Subject: Re: [Live-devel] RTSPClient::fBaseURL and RTSPClient::sessionURL()
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() availab
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 f
ight be called
from RTSPClient object, thus this is not a good option.
Kind regard,
Dmitriy
- Original Message -
From: Ross Finlayson
To: LIVE555 Streaming Media - development & use
Sent: Thursday, December 02, 2010 1:38 AM
Subject: Re: [Live-devel] RTSPClient::fBaseURL an
I'm trying to write RTSP client which will be able to read from
multiple URLs simultaneously using the single event loop.
Note that a single "RTSPClient" object is used for controlling *one*
stream (i.e., one "rtsp://" URL) only. Your RTSP client
*application* can, of course, open and play mu
Hello Ross,
I'm trying to write RTSP client which will be able to read from multiple URLs
simultaneously using the single event loop.
Is there any way to identify session URL in RTSPClient response handlers? These
handlers receive pointer to RTSPClient object. Unfortunatelly, the related
class
