accept(ListenSocket, NULL, NULL); cause program to hang?

hi....

Accroding to MSDN:

http://msdn.microsoft.com/library/de...nd_servers.asp

the accept() method can be used such as:

accept(ListenSocket, NULL, NULL);

how ever I tried:

Code:

---

ClientSocket = accept(ListenSocket, NULL, NULL);
if (ClientSocket == INVALID_SOCKET) {
    printf("accept failed: %d\n", WSAGetLastError());
    closesocket(ListenSocket);
    WSACleanup();
    return 1;
}

---

my program hang/jam at:

ClientSocket = accept(ListenSocket, NULL, NULL);

so therefore accept(ListenSocket, NULL, NULL); cannot be used in such a way?

Thanks

Post a whole program, we can't tell what else you might have screwed up before then.

Like did you call WSAStartup() ?
Did you call listen() before accept() ?

accept() is a blocking function, meaning that it will not finish until it accept()s a connection or an error occurs. That's why your program seems to be jammed.

Quote:

---

Originally Posted by Salem

Post a whole program, we can't tell what else you might have screwed up before then.

Like did you call WSAStartup() ?
Did you call listen() before accept() ?

---

http://msdn.microsoft.com/library/de...erver_code.asp

Quote:

---

Originally Posted by Desolation

accept() is a blocking function, meaning that it will not finish until it accept()s a connection or an error occurs. That's why your program seems to be jammed.

---

thanks.... but is there a way to break after it accept?


Thanks

Quote:

---

Originally Posted by draggy

thanks.... but is there a way to break after it accept?

---

What exactly does that mean...?
Program execution will remain inside accept() until either the socket has an error, or until a client connects.

Otherwise, you could look into either use of select() or nonblocking sockets. Both take a bit more skill however.

Quote:

---

Originally Posted by Cactus_Hugger

What exactly does that mean...?
Program execution will remain inside accept() until either the socket has an error, or until a client connects.

Otherwise, you could look into either use of select() or nonblocking sockets. Both take a bit more skill however.

---

Thanks

ermm ......

one more thing can we send and recive without bind and connect?

Thanks

The function will fail with a WSAENOTCONN (not connected) error.

Quote:

---

one more thing can we send and recive without bind and connect?

---

If you are using UDP, then you can send and receive without calling connect(). You still need to call bind() though.

Quote:

---

Originally Posted by bithub

If you are using UDP, then you can send and receive without calling connect(). You still need to call bind() though.

---

Do we still need accept()?

Thanks

nope

Thanks