What exactly does listen() do from winsock 1.1

Hi, im designing a login server for a game, and every time the server receives a connection i intend to a launch a new thread. I was playing with the code from another server i made which was only capable of connecting to one client, and basically it does this.

Code:

---

//define the listening socket above
listen(listenSock, 10)
//define a server socket
serverSock = accept(listenSock, NULL, NULL);
//terminate server thread, as this is just a test

---

what i was expecting was the server thread to block at listen(), and then continue after the client tried to connect. The client, ofcourse, timed out. however, i then tried running two clients, and both of them found the server (im not sure if they both got "accepted") and then timed out.

So what does listen() actually. Im really confused, as i was intending to make a loop using listen to block until a client tried to connect and then launch a thread. But it would appear as though listen did more than just block. Could someone please explain whats going on there. Thanks.

listen() puts the socket in listening mode. It doesn't wait for an actual connection, though. That's accept()'s job.

listen() goes in the main thread, then you pass the accept()'ed socket into a new thread to deal with that connection. The main thread loops round for another listen.

ok, so accept() will block and should be in the loop, and theres some sort of magical queue created in the background. I hate magic, so confusing.

Thx, im pretty sure i can work from there.

There's no queue. Accept will block if the socket is blocking and won't if it's not. Where is this queue you are speaking of?

This queue is internal to the network driver and holds client connections until accept fetches them.

Ok there's no queue from a software standpoint. :)