| Dart Home | PowerTCP Winsock for ActiveX | Custom Development | Reply | PowerTCP Winsock for ActiveX Topics | Forums |
| Author | Forum: PowerTCP Winsock for ActiveX Topic: 64 socket limitation |
| rklenotiz From: Rochester, NY USA Posts: 19 Member Since: 08/08/03 |
posted March 25, 2004 1:44 PM On the Microsoft site, this info was posted: There are two limitations in Winsock where you're limited to 64 sockets. The Win32 event mechanism (e.g. WaitForMultipleObjects()) can only wait on 64 event objects at a time. Winsock 2 provides the WSAEventSelect() function which lets you use Win32's event mechanism to wait for events on sockets. Because it uses Win32's event mechanism, you can only wait for events on 64 sockets at a time. If you want to wait on more than 64 Winsock event objects at a time, you need to use multiple threads, each waiting on no more than 64 of the sockets. The select() function is also limited in certain situations to waiting on 64 sockets at a time. ---------------------------------------- How would this impact Dart Winsock Controls? What if I had an array of TCP controls on the server side, say 75 controls in an array. Does this 64 limitation effect Dart products?? Thank you. |
Tony Priest![]() From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted March 25, 2004 1:47 PM A question of this complexity will have to be reviewed by someone who actually does the underlying coding. I will make sure that they do that, but it will most likely take a few days. It would probably be quicker for you to run some tests at your end to determine what happens. |
| Reply | PowerTCP Winsock for ActiveX Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|