<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div style="" class=""><div class=""><div id="yiv4115415471yui_3_16_0_1_1438849490422_75379" dir="ltr" class="">We rely on a now-ancient version (2009-09-04) of LIVE555 Streaming Media library as the basis for the RTSP streaming server in our [open source] product. I'm trying to assess how feasible it would be to upgrade to the latest version of LIVE555 in the near future.</div></div></div></div></blockquote><div><br class=""></div>You should definitely upgrade. Not only do we not support old versions of the code, but (most importantly) newer versions fix several, often-important bugs, including security vulnerabilities. You are putting your system at great risk by continuing to use an old version (especially such an old version) of the code.</div><div><br class=""></div><div>(Once you’ve upgraded your open source product to use the latest version of the LIVE555 code, please let me know, and I’ll add a link to your project from our web page.)</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="" class=""><div class=""><div id="yiv4115415471yui_3_16_0_1_1438849490422_75379" dir="ltr" class=""> Obviously there are challenges, for example the changeover from the ancient synchronous API to the "new" asynchronous API.</div></div></div></div></blockquote><div><br class=""></div>You may be a bit confused here. The ‘asynchronous API’ applies only to “RTSPClient” - i.e., to the RTSP client implementation. If your system uses our code only to implement a RTSP *server*, then this has not been an issue; our RTSP server has always been able to handle multiple clients asynchronously.</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="" class=""><div class=""><div id="yiv4115415471yui_3_16_0_1_1438849490422_75597" dir="ltr" class="">As part of the product, we have a configuration section/panel that enables administrators to see the list of "clients" connected to the server. The list includes [for each "client"]: the client session ID, the client IP address, the server session ID that the client is accessing, and some additional metadata about the server session media. The administrator can choose to "kick" (drop) client sessions if they deem it appropriate.</div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75693" dir="ltr" class=""> </div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75709" dir="ltr" class="">In the version of LIVE555 that we're currently using, the fClientAddr and <span class="yiv4115415471">fOurSessionId are encapsulated in a single</span><br class=""><span class="yiv4115415471">RTSPClientSession class. Therefore the correlation between the 2 pieces of information is obvious, and we have no problem building the list. However, in the latest code these key pieces of information are split between RTSPClientSession and RTSPClientConnection. I can't see how to correlate the instances of these classes, especially since createNewClientSession() no longer provides the </span>clientAddr parameter.</div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75979" dir="ltr" class=""> </div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75981" dir="ltr" class="">So, in short my question is: how can I get the <span class="yiv4115415471">RTSPClientConnection instance associated with a given </span><span class="yiv4115415471">RTSPClientSession? If it isn't possible, can you point me to an explanation of why the design was changed in such a way as to make it not possible.</span></div></div></div></div></blockquote><div><br class=""></div>The design was changed because the old design was predicated on the incorrect assumption (one that you also made) that each ‘client session’ is tied to exactly one ‘client connection’. That is incorrect. The RTSP protocol allows a single client connection (i.e., TCP connection to the RTSP server) to be used to send commands for completely different streams (and thus different client sessions). It is also possible to use different TCP connections to send separate RTSP commands - i.e., use one TCP connection to send “DESCRIBE”; another to send “SETUP”; another to send “PLAY”, etc. - all for the same ‘client session’. It is even possible, in principle, for these requests (within the same ‘client session’) to be sent from different client IP addresses, although I don’t know if anyone actually does this. But it is possible.</div><div><br class=""></div><div>In short: The RTSP protocol completely separates ‘client connections’ and ‘client connections’, and our implementation now reflects this.</div><div><br class=""></div><div>So, you’ll see that 'client IP address' isn’t a particularly useful piece of information to have for each ‘client session’ (because it can, in principle, change, for each command). If, however, you really want to get the 'client IP address' that was used to send a particular command, you could do so by subclassing “RTSPServer” and “RTSPClientSession”, and reimplementing the virtual function that implements that particular command - e.g., "RTSPServer::RTSPClientSession::handleCmd_PLAY()”. This function takes a "RTSPServer::RTSPClientConnection*” as parameter; you could get the ‘client IP address’ from this parameter. (“fClientAddr” is actually a protected field in "RTSPServer::RTSPClientConnection”, so you would probably need to subclass that as well, in order to get access to it.)</div><br class=""><br class=""><div apple-content-edited="true" class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Ross Finlayson<br class="">Live Networks, Inc.<br class=""><a href="http://www.live555.com/" class="">http://www.live555.com/</a></span></span>
</div>
<br class=""></body></html>