Why doesn't my GetQueuedCompletionStatus return in IOCP?

zuanzuan

I use
(1) accept accepted the connection
(2) CreateIoCompletionPort () adds the connection to the completion port
Why does GetQueuedCompletionStatus not return after the client (telnet) is connected?

爱德华德

Did the server accept the client's connection and then post the receive operation?

zuanzuan

Ask upstairs, what is: "Received delivery operation"?

爱德华德

WSARecv operation, did you do it

lixiaof6471

What about the code?
Can read about Windows network programming
Or visit
www.codeproject.com/internet

zuanzuan

Brothers, I posted a lot of code, too annoying, I used the爱德华德suggestion, and the current process becomes
Accept when there is a connection
2. WSARecv ()-returns 997
3. Call CreateIoCompletionPort () to add acceptedSock to the completion port

4. In the worker thread, after GetQueuedCompletionStatus () returns, call WSARecv (), always returning 997

What solution?

爱德华德

WSARecv returns 997 is normal

爱德华德

Not an error, this is a characteristic of the completion port

xop000

Accept when there is a connection
2. WSARecv ()-returns 997
3. Call CreateIoCompletionPort () to add acceptedSock to the completion port

==>

Accept when there is a connection
2. Call CreateIoCompletionPort () to add acceptedSock to the completion port
3. WSARecv ()-returns 997

zuanzuan

Thank you all for your help, I finally want to take a big step forward and I can receive data from the client. I found that WSARecv () called after accept is equivalent to setting the buffer and other things, and GetQueuedCompletionStatus uses these things to fill the buffer. If the buffer is large enough, WSARecv () after GetQueuedCompletionStatus () is not necessary. Conversely, if the buffer is not large enough, WSARecv () is necessary, and each time WSARecv () will affect the buffer of GetQueuedCompletionStatus ().
Not all the inside story of IOCP is clear, but it is already moving forward.

toxop000:
  I also think it should be your order, but I can still follow the previous order. Presumably the functions of Winsock are smart enough? Information is stored in the system when WSARecv () is called, so calling CreateIoCompletionPort () afterwards can also IO normally?
  Is there a master to share the inside story?