LPNSPIOCTL callback function (ws2spi.h)
The NSPIoctl function sends an IOCTL to a namespace service provider.
Syntax
LPNSPIOCTL Lpnspioctl;
INT Lpnspioctl(
[in] HANDLE hLookup,
[in] DWORD dwControlCode,
[in] LPVOID lpvInBuffer,
[in, out] DWORD cbInBuffer,
[out] LPVOID lpvOutBuffer,
[in] DWORD cbOutBuffer,
[out] LPDWORD lpcbBytesReturned,
[in] LPWSACOMPLETION lpCompletion,
[in] LPWSATHREADID lpThreadId
)
{...}
Parameters
[in] hLookup
The lookup handle returned from a previous call to the NSPLookupServiceBegin function.
[in] dwControlCode
The control code of the operation to perform.
The values that may be used for the dwControlCode parameter are determined by the namespace provider.
The following value is supported by several Microsoft namespace providers including the Network Location Awareness (NS_NLA) namespace provider. This IOCTL is defined in the Winsock2.h header file.
| Value | Meaning |
|---|---|
|
This operation checks if the results returned with previous calls using the hLookup parameter are still valid. These previous calls include the initial call to the NSPLookupServiceBegin function to retrieve the hLookup parameter. These previous calls may also include calls to the NSPLookupServiceNext function using the hLookup parameter. |
[in] lpvInBuffer
A pointer to the input buffer.
[in, out] cbInBuffer
The size, in bytes, of the input buffer.
[out] lpvOutBuffer
A pointer to the output buffer.
[in] cbOutBuffer
The size, in bytes, of the output buffer.
[out] lpcbBytesReturned
A pointer to the number of bytes returned.
[in] lpCompletion
A pointer to a WSACOMPLETION structure, used for asynchronous processing. Set lpCompletion to NULL to force blocking (synchronous) execution.
[in] lpThreadId
A pointer to a WSATHREADID structure to be used by the provider in a subsequent call to WPUQueueApc. The provider should store the referenced WSATHREADID structure (not the pointer) until after the WPUQueueApc function returns.
Return value
If no error occurs and the operation has completed immediately, the NSPIoctl function should return NO_ERROR (zero). Note that in this case the completion routine, if specified, will have already been queued.
The NSPIoctl function should return SOCKET_ERROR (that is, 1) if the routine fails and it must set the appropriate error code using WSASetLastError.
The error code WSA_IO_PENDING indicates that an overlapped operation has been successfully initiated and that completion will be indicated at a later time. Any other error code indicates that no overlapped operation was initiated and no completion indication will occur.
| Error code | Description |
|---|---|
| The hLookup parameter was not a valid query handle returned by NSPLookupServiceBegin. | |
| An overlapped operation was successfully initiated and completion will be indicated at a later time. | |
| The lpvInBuffer, cbInBuffer, lpvOutBuffer, cbOutBuffer, or lpCompletion argument is not totally contained in a valid part of the user address space. Alternatively, the cbInBuffer or cbOutBuffer argument is too small, and the argument is modified to reflect the required allocation size. | |
| A supplied parameter is not acceptable, or the operation inappropriately returns results from multiple namespaces when it does not make sense for the specified operation. | |
| The network subsystem has failed. | |
| The operation is not supported. This error is returned if the namespace provider does not implement this function. This error can also be returned if the specified dwControlCode is an unrecognized command. | |
|
The resource is temporarily unavailable. The socket is not using overlapped I/O (asynchronous processing), yet the lpCompletion parameter is non-**NULL**.
This error is used as a special notification for the SIO_NSP_NOTIFY_CHANGE IOCTL when the lpCompletion parameter is NULL (a poll) to indicate that a query set remains valid. |
Remarks
The NSPIoctl function is used to send an I/O control code to a namespace provider in order to set or retrieve operating parameters associated with a query handle. The hLookup parameter is a handle to the namespace provider query previously returned by the NSPLookupServiceBegin function (not a socket handle).
Any IOCTL sent to a namespace provider may block indefinitely, depending upon the implementation of the namespace. If an application cannot tolerate blocking in a NSPIoctl function call, overlapped I/O should be used and the lpCompletion parameter should point to a WSACOMPLETION structure. To make a NSPIoctl function call nonblocking and return immediately, set the Type member of the WSACOMPLETION structure to NSP_NOTIFY_IMMEDIATELY.
If lpCompletion is NULL, the NSPIoctl function executes as a blocking call. The namespace provider should return immediately and should not block. But each namespace provider is responsible for enforcing this behavior.
The following IOCTL code is supported by several Microsoft namespace providers:
The Microsoft namespace providers that support this IOCTL include the following:
- NS_NLA - The Network Location Awareness (NLA) namespace provider.
- NS_PNRPNAME - The Peer Name Resolution Protocol (PNRP) namespace provider.
- NS_PNRPCLOUD - The Peer Name Resolution Protocol (PNRP) cloud namespace provider.
Other non-Microsoft namespace providers may be installed that also support this IOCTL.
When the lpCompletion parameter is NULL, this IOCTL implements a special behavior. If the lpCompletion parameter is NULL for this IOCTL, this operation is a poll and returns immediately. If the query set remains valid, WSAEWOULDBLOCK is returned as notification that the query set remains valid. If the query set has changed and is invalid, NO_ERROR is returned indicating success in polling for invalidation of the query set.
If the lpCompletion parameter is not NULL and points to an WSACOMPLETION structure, then the NSPIoctl function returns WSA_IO_PENDING if the overlapped operation was successfully initiated and completion will be indicated at a later time. The method specified in the WSACOMPLETION structure is used to notify the application if the query set is still valid.
Not all name resolution protocols are able to support this feature, and therefore, this function call may fail with WSAEOPNOTSUPP. A query containing data from multiple providers cannot call this IOCTL, and will return WSAEINVAL.
The lpvInBuffer, cbInBuffer, lpvOutBuffer, and cbOutBuffer parameters are currently ignored by Microsoft namespace providers.
For single-threaded applications, a typical method to use the NSPIoctl function is as follows. Call the NSPIoctl function with the dwControlCode parameter set to SIO_NSP_NOTIFY_CHANGE with no completion routine (the lpCompletion parameter set to NULL) after every NSPLookupServiceNext function call to make sure the query data is still valid. If the data becomes invalid, call the NSPLookupServiceEnd function to close the query handle. Call the NSPLookupServiceBegin function to retrieve a new query handle and begin the query again.
For multithreaded applications, a typical method to use the NSPIoctl function is as follows. Call the NSPIoctl function with the dwControlCode parameter set to SIO_NSP_NOTIFY_CHANGE with a completion routine after the initial call to the NSPLookupServiceBegin function. The application would use the mechanism for notification specified in the completion routine to be notified when data is no longer valid. One common mechanism is to use an event specified in the completion routine. If the data becomes invalid, call the NSPLookupServiceEnd function to close the query handle. Call the NSPLookupServiceBegin and the NSPIoctl functions to retrieve a new query handle and begin the query again.
Some protocols may simply cache the information locally and invalidate it after some time, in which case notification may be issued to indicate the local cache has been invalidated.
For name resolution protocols where changes are infrequent, it is possible for a namespace provider to indicate a global change event that may not be applicable to the query on which change notification was requested and issued.
Immediate poll operations are usually much less resource intensive since they do not require a notification object. In most cases, this is implemented as a simple Boolean variable check. Asynchronous notification, however, may necessitate the creation of dedicated worker threads and/or inter-process communication channels, depending on the implementation of the namespace provider service, and will incur processing overhead related to the notification object involved with signaling the change event.
To cancel an asynchronous notification request, end the original query with a NSPLookupServiceEnd function call on the affected query handle. Canceling the asynchronous notification for LUP_NOTIFY_HWND will not post any message, however, an overlapped operation will be completed and notification will be delivered with the error WSA_OPERATION_ABORTED.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client | Windows XP [desktop apps only] |
| Minimum supported server | Windows Server 2003 [desktop apps only] |
| Target Platform | Windows |
| Header | ws2spi.h |