www.delorie.com/archives/browse.cgi | search |
On Mon, Dec 06, 1999 at 04:17:28PM -0500, Chris Faylor wrote: >On Mon, Dec 06, 1999 at 09:54:39AM -0600, Mumit Khan wrote: >>stefan <stefan AT linux DOT f1 DOT fhtw-berlin DOT de> writes: >>> Hello, >>> >>> we were porting a server software to Win9x/NT and had to notice that you >>> cannot accept() more than 64 sockets. Why is this ? Can anyone help us ? >> >>The underlying OS API, WaitForMultipleObjects, has a limit of 64 handles >>it can wait on, and that's probably the reason. There are tricks to get >>around it, but it requires creating multiple threads. Not pretty. > >This isn't a problem with cygwin. Cygwin uses the Winsock select() for >sockets. There probably is a limit there but it's not 64. Just to clarify: The "This" above refers to the WaitForMultipleObjects limit of 64 handles. This particular hard limit probably does not affect cygwin. There is a hard-coded limit in winsock.h which is probably what is coming to play here. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |