<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head><body style=""><div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75307">Hello</div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75390"> </div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75379" dir="ltr">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. Obviously there are challenges, for example the changeover from the ancient synchronous API to the "new" asynchronous API. I think I should be able to figure most things out given a bit of time. However, after a day of staring at code I've found one problem that I can't see how to solve.</div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75595"> </div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75597" dir="ltr">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"> </div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75709" dir="ltr">In the version of LIVE555 that we're currently using, the fClientAddr and <span class="yiv4115415471">fOurSessionId are encapsulated in a single</span><br><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"> </div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75981" dir="ltr">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 id="yiv4115415471yui_3_16_0_1_1438849490422_76039" dir="ltr"><br><span class="yiv4115415471"></span></div>
<span class="yiv4115415471">Thanks in advance!</span></div></body></html>