PFN_WSK_RECEIVE_EVENT callback function (wsk.h)
The WskReceiveEvent event callback function notifies a WSK application that data has been received on a connection-oriented socket.
Syntax
PFN_WSK_RECEIVE_EVENT PfnWskReceiveEvent;
NTSTATUS PfnWskReceiveEvent(
[in, optional] PVOID SocketContext,
[in] ULONG Flags,
[in, optional] PWSK_DATA_INDICATION DataIndication,
[in] SIZE_T BytesIndicated,
[in, out] SIZE_T *BytesAccepted
)
{...}
Parameters
[in, optional] SocketContext
A pointer to the socket context for the connection-oriented socket that has received the data. The WSK application provided this pointer to the WSK subsystem in one of the following ways:
- It called the WskSocket function to create the socket.
- It called the WskSocketConnect function to create the socket.
- It called the WskAccept function to accept the socket as an incoming connection.
- Its WskAcceptEvent event callback function was called to accept the socket as an incoming connection.
[in] Flags
A ULONG value that contains a bitwise OR of a combination of the following flags:
| Value | Meaning |
|---|---|
|
The data buffers that contain the received data should not be retained by the WSK application if at all possible. If the WSK application retains the buffers, it should release them as soon as possible by calling the WskRelease function. |
|
The data buffers contain either an entire message or the final portion of a message. The interpretation of what constitutes an entire message is transport protocol-specific. For TCP, this flag indicates that the push bit was set for one or more of the TCP segments that constitute the data in the data buffers. |
|
The WSK subsystem called the WskReceiveEvent event callback function at IRQL = DISPATCH_LEVEL. If this flag is not set, the WSK subsystem might have called the WskReceiveEvent event callback function at any IRQL <= DISPATCH_LEVEL. |
[in, optional] DataIndication
A pointer to a linked list of WSK_DATA_INDICATION structures that describe the received data. If this parameter is NULL, the socket is no longer functional and the WSK application must call the WskCloseSocket function to close the socket as soon as possible.
[in] BytesIndicated
The number of bytes of received data described by the linked list of WSK_DATA_INDICATION structures.
[in, out] BytesAccepted
A pointer to a SIZE_T-typed variable which receives the number of bytes of received data that is accepted by the WSK application. This variable needs to be set only if the WSK application accepts a portion of the total number of bytes of received data. If the WSK application accepts all of the received data, it does not have to set this variable. If the WskReceiveEvent event callback function returns a status other than STATUS_SUCCESS, the WSK subsystem ignores the value of this variable.
Return value
A WSK application's WskReceiveEvent event callback function can return one of the following NTSTATUS codes:
| Return code | Description |
|---|---|
|
The WSK application accepted at least some of the received data. If the WSK application accepted all of the received data, the WSK subsystem can call the WskReceiveEvent event callback function again when new data is received on the socket. However, if the WSK application accepted only a portion of the received data, the WSK subsystem will not call the WskReceiveEvent event callback function again until after the WSK application calls the WskReceive function. After the WSK application calls the WskReceive function, the WSK subsystem will resume calling the WskReceiveEvent event callback function with any remaining buffered data and when new data is received on the socket. A WSK application can call the WskReceive function with a zero-length buffer, which will cause the WSK subsystem to resume calling the WskReceiveEvent event callback function without calling WskReceive to receive any data from the socket. |
|
The WSK application accepted the data but did not retrieve all of the data contained in the linked list of WSK_DATA_INDICATION structures. The WSK application retains the linked list of WSK_DATA_INDICATION structures until all of the data has been retrieved. After the WSK application has retrieved all of the data it calls the WskRelease function to release the linked list of WSK_DATA_INDICATION structures back to the WSK subsystem. The WSK subsystem can call the WskReceiveEvent event callback function again when new data is received on the socket. |
|
The WSK application did not accept the data. In this situation, the WSK subsystem will have the underlying transport buffer the data if possible or if otherwise required by the protocol. The WSK subsystem will not call the WskReceiveEvent event callback function again until after the WSK application calls the WskReceive function. After the WSK application calls the WskReceive function, the WSK subsystem will resume calling the WskReceiveEvent event callback function with any remaining buffered data and when new data is received on the socket. A WSK application can call the WskReceive function with a zero-length buffer, which will cause the WSK subsystem to resume calling the WskReceiveEvent event callback function without calling WskReceive to receive any data from the socket. |
Remarks
The WSK subsystem calls a WSK application's WskReceiveEvent event callback function when new data is received on a connection-oriented socket only if the event callback function was previously enabled with the SO_WSK_EVENT_CALLBACK socket option. For more information about enabling a socket's event callback functions, see Enabling and Disabling Event Callback Functions.
If a WSK application's WskReceiveEvent event callback function is enabled on a connection-oriented socket and the application also has a pending call to the WskReceive function on the same connection-oriented socket, then, when data arrives, the pending call to the WskReceive function will take precedence over the WskReceiveEvent event callback function. The WSK subsystem calls the application's WskReceiveEvent event callback function only if there are no IRPs queued from pending calls to the WskReceive function. However, a WSK application should not assume that the WSK subsystem will not call the application's WskReceiveEvent event callback function for a connection-oriented socket that has a pending call to the WskReceive function. Race conditions exist where the WSK subsystem could still call the WSK application's WskReceiveEvent event callback function for the socket. The only way for a WSK application to ensure that the WSK subsystem will not call the application's WskReceiveEvent event callback function for a connection-oriented socket is to disable the application's WskReceiveEvent event callback function on the socket.
Note
Winsock Kernel (WSK) calls this callback serially, so it is not always invoked as soon as data is received.
The WSK subsystem calls a WSK application's WskReceiveEvent event callback function at IRQL <= DISPATCH_LEVEL.
A WSK application's WskReceiveEvent event callback function must not wait for completion of other WSK requests in the context of WSK completion or event callback functions. The callback can initiate other WSK requests (assuming that it doesn't spend too much time at DISPATCH_LEVEL), but it must not wait for their completion even when the callback is called at IRQL = PASSIVE_LEVEL.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client | Available in Windows Vista and later versions of the Windows operating systems. |
| Target Platform | Windows |
| Header | wsk.h (include Wsk.h) |
| IRQL | <= DISPATCH_LEVEL |