> I may be missing something but I can't see how > wSockets.Count will ever not equal 1 up until the > first connection is established. This means the CPU > jumps to 100% until a connection is established! Yes. If you establish a connection and send no data that happens. -Gonzalo