LPNSPV2STARTUP callback function (ws2spi.h)
The NSPv2Startup function notifies a namespace service provider version-2 (NSPv2) provider that a new client process is to begin using the provider.
Syntax
LPNSPV2STARTUP Lpnspv2startup;
INT Lpnspv2startup(
[in] LPGUID lpProviderId,
[in] LPVOID *ppvClientSessionArg
)
{...}
Parameters
[in] lpProviderId
A pointer to the GUID of the specific namespace provider to notify.
[in] ppvClientSessionArg
A pointer to the client session.
Return value
The function should return NO_ERROR (zero) if the routine succeeds. It should return SOCKET_ERROR (that is, 1) if the routine fails and it must set the appropriate error code using WSASetLastError.
| Error code | Meaning |
|---|---|
| There is not enough memory available to perform this operation. | |
| The calling routine does not have sufficient privileges to initialize the service. | |
| One or more parameters were invalid, or missing, for this provider. | |
| The operation is not supported. This error is returned if the namespace provider does not implement this function. | |
| Service is unknown. The service cannot be found in the specified namespace. |
Remarks
The NSPv2Startup function is used as part of the namespace service provider version-2 (NSPv2) architecture available on Windows Vista and later.
On Windows Vista and Windows Server 2008, the NSPv2Startup function can only be used for operations on NS_EMAIL namespace providers.
The NSPv2Startup function is called each time a new client process begins using namespace provider. Providers may use the client session argument pointed to by the ppvClientSessionArg parameter to store information about this session. The value in the ppvClientSessionArg parameter will be passed to subsequent NSPv2 function calls in the same session. The client session argument may NULL, if the namespace provider does not require this information.
The NSPv2Startup function is called when a new client session initializes. The NSPv2Startup and NSPv2Cleanup functions must be called as pairs.
The NSPv2Startup function must be called successfully before calling the NSPv2Cleanup function. It is permissible to make more than one NSPv2Startup call. However, for each NSPv2Startup call, a corresponding NSPv2Cleanup call must also be issued. Only the final NSPv2Cleanup for the service provider does the actual cleanup; the preceding calls decrement an internal reference count in the namespace service provider.
The NSPv2Startup, NSPv2ClientSessionRundown, and NSPv2Cleanup functions are optional, dependent on the requirements of the NSPv2 provider.
If the NSPv2Startup function isn't implemented, then calls to that function should be intercepted by a stub function that returns WSAEOPNOTSUPP. The NSPv2 function pointer to the unimplemented NSPv2Startup function in the NSPV2_ROUTINE structure should point be to the stub function.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client | Windows Vista [desktop apps only] |
| Minimum supported server | Windows Server 2008 [desktop apps only] |
| Target Platform | Windows |
| Header | ws2spi.h |