Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The socket IOCTL opcodes for Winsock are summarized in the following table. More detailed information is provided in section 4 under WSPIoctl. There are other new protocol-specific IOCTL opcodes that can be found in the protocol-specific annex.
Opcode | Input type | Output type | Description |
---|---|---|---|
FIONBIO |
Unsigned long |
<Not used> |
Enables or disables nonblocking mode on the socket. |
FIONREAD |
<Not used> |
Unsigned long |
Determines the amount of data that can be read atomically from the socket. |
SIO_GET_BROADCAST_ADDRESS |
<Not used> |
sockaddr |
Retrieves the protocol-specific broadcast address to be used in WSPSendTo. |
SIO_MULTIPOINT_LOOKBACK |
BOOL |
<Not used> |
Controls whether data sent in a multipoint session will also be received by the same socket on the local host. |
SIO_MULTICAST_SCOPE |
int |
<Not used> |
Specifies the scope over which multicast transmissions will occur. |
SIO_ROUTING_INTERFACE_QUERY |
sockaddr |
sockaddr |
Obtains the address of the local interface that should be used to send to the specified address. |
SIO_ROUTING_INTERFACE_CHANGE |
sockaddr |
<Not used> |
Requests notification of changes in information reported through SIO_ROUTING_INTERFACE_QUERY for the specified address. |
SIO_ADDRESS_LIST_QUERY |
<Not used> |
SOCKET_ADDRESS_LIST |
Obtains the list of addresses to which the application can bind. |
SIO_ADDRESS_LIST_CHANGE |
<Not used> |
<Not used> |
Requests notification of changes in information reported through SIO_ADDRESS_LIST_QUERY. |
See Also
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.