That I understand, what I don't understand is what that process has to do with the actual socket. It seems like the model should be: start each connection on its own thread -- that thread is in control of the connection. If any data is recived by any thread then assign that to a "queue" (shared var or vars) and then have each of the other threads that are masters of their connection's read off that queue and push out the data on their connection. I just dont get what bennifet sharing the connection object has in that view of things.
in reply to Re^2: share socket connections amongst multiple threads?
in thread share socket connections amongst multiple threads?