The WSPShutdown function disables sends and/or receives on a socket.
int WSPShutdown( _In_ SOCKET s, _In_ int how, _Out_ LPINT lpErrno );
Descriptor identifying a socket.
Flag that describes what types of operation will no longer be allowed.
Pointer to the error code.
If no error occurs, WSPShutdown returns zero. Otherwise, a value of SOCKET_ERROR is returned, and a specific error code is available in lpErrno.
The network subsystem has failed.
The how is not valid, or is not consistent with the socket type. For example, SD_SEND is used with a UNI_RECV socket type.
Function is invoked when a callback is in progress.
Socket is not connected (connection-oriented sockets only).
The descriptor is not a socket.
The WSPShutdown function is used on all types of sockets to disable reception, transmission, or both.
If how is SD_RECEIVE, subsequent receives on the socket will be disallowed. This has no effect on the lower protocol layers. For TCP sockets, if there is still data queued on the socket waiting to be received, or data arrives subsequently, the connection is reset, since the data cannot be delivered to the user. For UDP sockets, incoming datagrams are accepted and queued. In no case will an ICMP error packet be generated.
If how is SD_SEND, subsequent sends on the socket are disallowed. For TCP sockets, a FIN will be sent. Setting how to SD_BOTH disables both sends and receives as described above.
Note that WSPShutdown does not close the socket, and resources attached to the socket will not be freed until WSPCloseSocket is invoked.
Note The WSPShutdown function does not block regardless of the SO_LINGER setting on the socket. A Windows Sockets SPI client should not rely on being able to reuse a socket after it has been shut down. In particular, a Windows Sockets service provider is not required to support the use of WSPConnect on such a socket.
Minimum supported client
Windows 2000 Professional [desktop apps only]
Minimum supported server
Windows 2000 Server [desktop apps only]