Upcalls Exposed by Ws2.dll
A version of this page is also available for
4/8/2010
This section lists the upcalls that service providers may make into the Windows Sockets client. Service providers receive an upcall dispatch table as a parameter to WSPStartup, and use entries in this table to make the upcalls. Therefore, a client does not need to export its WPU functions.
It is not mandatory that providers use all of these upcalls. The following table indicates which upcalls must be used and which are optional.
| Function | Description | Status | Significance |
|---|---|---|---|
Closes an open event object handle. |
Optional. |
The provider may use an appropriate OS call instead. |
|
Closes a socket handle allocated by the Windows Sockets DLL. |
Required. |
Ws2.dll needs to query and/or modify internal state information associated with the socket handle. |
|
Creates a new event object. |
Optional. |
The provider may use an appropriate OS call instead. |
|
Creates a new socket handle for non-IFS providers. |
Required for non-IFS providers. |
Ws2.dll needs to query and/or modify internal state information associated with the socket handle. |
|
Checks the membership of the specified socket handle. |
Optional. |
This is just a convenience function that knows how to dig through FD SET structures. A provider may need to dig through these structures explicitly anyway. |
|
Retrieves a socket's context value (non-IFS providers only). |
Required for non-IFS providers. |
Ws2.dll needs to query and/or modify internal state information associated with the socket handle. |
|
Resets an event object. |
Optional. |
The provider may use an appropriate OS call instead. |
|
Sets an event object. |
Optional. |
The provider may use an appropriate OS call instead. |