<!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>Thank you very much for your prompt and helpful response Ross.</div>
<div> </div>
<blockquote type="cite" style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;">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.</blockquote>
<p>Yes, I understand the risks and implications and will do everything within my power to push us through an upgrade. Unfortunately I'm only a lowly developer, and so some decisions are not in my control.</p>
<p> </p>
<blockquote type="cite" style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;">
<div> </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>
</blockquote>
<p>Sure, I'll do that. Thank you.</p>
<p> </p>
<blockquote type="cite" style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;">
<div> </div>
<div><br>
<blockquote type="cite">
<div>
<div>
<div>
<div id="yiv4115415471yui_3_16_0_1_1438849490422_75379" dir="ltr">Obviously there are challenges, for example the changeover from the ancient synchronous API to the "new" asynchronous API.</div>
</div>
</div>
</div>
</blockquote>
<div> </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>
</blockquote>
<p>You're right, I didn't explain well. We do in fact have a two client implementations as well as the server implementation. So ultimately I will have to deal with this challenge... twice. Ahh well, such is life! :)</p>
<p> </p>
<blockquote type="cite" style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;">
<div> </div>
<div><br>The design was changed because...</div>
</blockquote>
<p>Thank you for the excellent explanation. I understand.</p>
<p>In our particular environment we always have a one-to-one relationship between sessions and connections. Therefore I will take your advice: implement the necessary sub-classes, and acquire the client IP address from either the SETUP or PLAY commands.</p>
<div> </div></body></html>