Question

I have read that working with more than 64 sockets in a thread is dangerous(?). But -at least for me- Non-blocking sockets are used for avoiding complicated thread things. Since there is only one listener socket, how am i supposed to split sockets into threads and use them with select() ? Should i create fd_sets for each thread or what ? And how am i supposed to assign a client to a thread, since I can only pass values in the beginning with CreateThread() ?

Answer 1

No no no, you got a few things wrong there.

First, the ideal way to handle many sockets is to have a thread pool which will do the work in front of the sockets (clients).
Another thread, or two (actually in the amount of CPUs as far as I know), do the connection accepting.

Now, when a an event occurs, such as a new connection, it is being dispatched to the thread pool to be processed.

Second, it depends on the actual implementation and environment.
For example, in Windows there’s something called IOCP.

If you ask me – do not bother with the lower implementation but instead use a framework such as BOOST::ASIO or ACE.

I personally like ASIO. The best thing about those frameworks is that they are usually cross-platform (nix, Windows etc’).

So, my answer is a bit broad but I think it’s to the best that you take these facts into consideration before diving into code/manuals/implementation.

Good luck!