That code is a no go.. :(
That code only "waits" for the data to send. This works on one connection, but there is a bug with an array of connections that makes the previously connected connectiosn NOT get their data (it queues instead of sends it)... It will send the data, if it recieves some data from that client, so constantly pinging the server "works", but is obviously very inefficient.. All that code will do is wait indefinately until it can send it (which it won't be able to do because of that bug.. :(
Thanks anyway..
Socket Wrench vs. Winsock
This problem only occurs with the Winsock control. My friend had a problem very much like this, and he simply switched to the Catalyst Socket Wrench control. It has a lot more features than Winsock (slightly more complex too.) You can download the control for free at http://www.catalyst.com/
Catalyst makes controls for just about every protocol, so make sure you get the right one (TCP/IP.) It is a great control and I have never once gone back to using the Winsock control since I have used Socket Wrench.
~Stoinker~