<div dir="ltr">Ross,<div><br></div><div>Very nice...I look forward to seeing how this evolves. </div><div><br></div><div>I noticed that you implemented the ability to specify stream suffix! I will be setting up a new test environment with the latest code base to work through these API changes. I'll provide feedback, should I encounter anything of interest.</div>
<div><br></div><div>Since this an initial draft, I assume your still open for comments/suggestions :-)</div><div><br></div><div>- Proxy Server -T option does not allow for specifying a unique port per stream. In NAT cases streams would have different ports. Would it be possible to have this option for streams that will be using RTSP over HTTP.</div>
<div>- Not sure if this would make sense, but would an UN-REGISTER method further enhance the capabilities of Proxy Server? This would allow for a perpetually running server that could dynamically REGISTER/UN-REGISTER streams as needed.</div>
<div><br></div><div>Bob </div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 18, 2013 at 5:03 AM, Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">FYI, I have just submitted to the IETF a new Internet-Draft document that describes our new custom "REGISTER" RTSP command (that we use in our proxy server implementation). You can find a copy online at<div>
<span style="white-space:pre-wrap"> </span><a href="http://tools.ietf.org/html/draft-finlayson-rtsp-register-command-00" target="_blank">http://tools.ietf.org/html/draft-finlayson-rtsp-register-command-00</a></div><div><br>
</div><div>I have also released a new version (2013.10.18) of the "LIVE555 Streaming Media" code that changes the implementation to conform to this document. In particular:</div><div>- There are no longer separate "REGISTER" and "REGISTER_REMOTE" commands. Now, there's only "REGISTER". An optional Boolean parameter "reuse_connection" - in the RTSP "Transport:" header - can be used to specify whether the recipient should reuse the TCP connection.</div>
<div>- There is a new optional parameter "proxy_url_suffix" (again, in the RTSP "Transport:" header) that can be used to specify the URL suffix that the receiving proxy server should use to advertise the proxied stream.</div>
<div><br></div><div>If you are "REGISTER"ing one of your "RTSPServer"s own streams (e.g., with a proxy server), then note that the "RTSPServer::registerStream()" API has changed.</div><div><br>
</div><div>If you are using a 3rd-party application to construct and send "REGISTER" commands - as Bob Bischan is doing - then note that</div><div>- The command to send is now "REGISTER", not "REGISTER_REMOTE", and</div>
<div>- There are optional parameters that you can specify in a RTSP "Transport:" header.</div><span class="HOEnZb"><font color="#888888"><br><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px">Ross Finlayson<br>
Live Networks, Inc.<br><a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a></span></span>
</div>
<br></font></span></div><br>_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a></blockquote><div> </div></div><p><br></p></div></div>