I think that’s a misdiagnosis of the issue there. That bit of code is sizing the read buffer not limiting the number of connections. I’d start by logging the result and socketError to see if that sheds any light. However I think the info here will sort it:
https://social.technet.microsoft.com/Forums/en-US/69449ce9-ea58-48ec-b675-c55480ba4bbb/windows-server-2012-and-tcpip-maxuserport?forum=winserverPN <https://social.technet.microsoft.com/Forums/en-US/69449ce9-ea58-48ec-b675-c55480ba4bbb/windows-server-2012-and-tcpip-maxuserport?forum=winserverPN> Cheers Monte > On 26 Apr 2019, at 4:54 pm, Richard Gaskin via use-livecode > <[email protected]> wrote: > > A forum user has an interesting use case involving sockets on a server that > needs to handle thousands of connections: > > https://forums.livecode.com/viewtopic.php?f=8&t=32515#p179090 > > He's discovered that livecode/engine/src/opensslsocket.cpp sets a limit on > sockets size to 16 bits. > > He's wondering if it could be raised to 32 bits. > > Anyone here know why this limit exists, or know of reasons that might make it > difficult to change? > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > [email protected] http://www.FourthWorld.com > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
