<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Live-devel] Receiving in multiple
threads</title></head><body>
<blockquote type="cite" cite>
<blockquote>1.<x-tab> </x-tab>My
understanding is that so long as each instance of the library uses its
own usageenvironment and event loop, it is ok to have multiple
instances in multiple threads (although I agree this is really not
advised).</blockquote>
</blockquote>
<div><br></div>
<div>Yes, this should work, in principle. However, it has not
been extensively tested, and I can't guarantee that there's not
still some inadvertently shared state somewhere. (If anyone
finds some, though, please let us know, and I'll try to remove
it.)</div>
<div><br></div>
<div>Have you tried putting your RTSP server in a separate *process*
from your input plugins. (Since your plugins are communicating
with the server via pipes, this should be straightforward, I
think...)</div>
<div><br></div>
<blockquote type="cite" cite>
<blockquote>3.<x-tab> </x-tab>Would it
make sense to add an optional base port for the client to use, similar
to RTSPServer?</blockquote>
</blockquote>
<div><br></div>
<div>No, because there's no standard port number for RTSP
*clients*.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>