<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div dir="auto">OK I didn't get it. I still don't understand why such a cause would be visible on a customer PC and not on a similar PC in our office. That doesn't make sense to me. But I'll gather some information about any such limitation.</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
<br>
</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
Reason for using Windows is that our software (a realtime 3D visualisation software) is originally based on Windows, and we had to add video streaming output for a very specific project, to replace the standard display output to monitor.</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
<br>
</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
Porting the whole codebase to Linux wasn't really an option to consider for that project (no money and no real need actually).</div>
<div id="mail-editor-reference-message-container" dir="auto"><br>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" style="font-size: 11pt;"><strong>De :</strong> live-devel <live-devel-bounces@us.live555.com> de la part de Ross Finlayson <finlayson@live555.com><br>
<strong>Envoyé :</strong> lundi 23 janvier 2023 à 18:19<br>
<strong>À :</strong> LIVE555 Streaming Media - development & use <live-devel@us.live555.com><br>
<strong>Objet :</strong> Re: [Live-devel] Connection to RTSP server failing after some time<br>
</div>
<br>
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><font size="2"><span style="font-size:11pt;">
<div class="PlainText"><br>
<br>
> On Jan 23, 2023, at 7:41 AM, g.jaegy <g.jaegy@imagine3d.fr> wrote:<br>
> <br>
> OK I keep that hint in mind as well.<br>
> <br>
<br>
> So according to the documentation I could gather, increasing that limit on Windows seems to consist in defining FD_SETSIZE with a higher value (default being 64) before including "Winsock2.h" header. I can easily do that in our code.<br>
> <br>
> I assume I'll however have to add that preprocessor definition in live555 code as well.<br>
<br>
No, FD_SETSIZE is already there. Should you modify that in a ‘winsock’ header file, you don’t need to alter the LIVE555 code; you just recompile it.<br>
<br>
But this is NOT what I was talking about when I said that perhaps "the server is running into an OS-imposed limit on the number of open sockets that a process can use”. I was referring to a limit within the Windows OS itself. You'd need to increase this limit
(which may or may not have anything to do with FD_SETSIZE) within Windows itself.<br>
<br>
But why on Earth are you running serious server code on Windows? I didn’t realize anyone did that anymore. You’re unlikely to encounter this problem if you run your server on Linux or FreeBSD.<br>
<br>
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/">http://www.live555.com/</a><br>
<br>
<br>
_______________________________________________<br>
live-devel mailing list<br>
live-devel@lists.live555.com<br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
</div>
</span></font><br>
</div>
</body>
</html>