recv() error during closing app

[Damon123]

how to deal with problem of closing my socket program when recv() ing data?

should I stop the recv() and flush the recv buffer so as to prevent recv() error?

[j0nas]

Do you need to stop a pending recv()?

Normally, you should know (by the application protocol) when to send and recv, and how much. Some application protocols, such as old HTTP version, don't specify content lengths, but rather close the socket when all data is sent or recv'd (the receiver gets zero back from recv(), known as graceful close).

You can't "flush" the input or output stream. You can however shutdown the down-stream end of your socket with shutdown(s, SD_RECEIVE). Read more about shutdown() on MSDN.

[MikeAThon]

Here's the MSDN recommendation for a graceful shutdown, as described at http://msdn.microsoft.com/library/en...shutdown_2.asp :

To assure that all data is sent and received on a connected socket before it is closed, an application should use shutdown to close connection before calling closesocket. For example, to initiate a graceful disconnect:
1. Call WSAAsyncSelect to register for FD_CLOSE notification.
2. Call shutdown with how=SD_SEND.
3. When FD_CLOSE received, call recv until zero returned, or SOCKET_ERROR.
4. Call closesocket.

Also check out the recommendations at "Graceful Shutdown, Linger Options, and Socket Closure" http://msdn.microsoft.com/library/en..._closure_2.asp

Mike