4.26 WFSAsyncUnlock

HRESULT WFSAsyncUnlock( hService, hWnd, lpRequestID )

Releases a service that has been locked by a previous WFSLock or WFSAsyncLock function. The asynchronous version of WFSUnlock.

Parameters HSERVICE hService

Handle to the service provider as returned by WFSOpen or WFSAsyncOpen.

HWND hWnd

The window handle which is to receive the completion message for this request.

LPREQUESTID lpRequestID

Pointer to the request identifier for this request (returned parameter).

Mode Aynchronous

Comments See WFSUnlock and Section 3.8.

The application must call WFSFreeResult to deallocate the WFSRESULT data structure which is pointed to by the completion message. Note that a WFSRESULT structure may be returned even if the function completes with an error; see Section 3.13.

Messages WFS_UNLOCK_COMPLETE

Error Codes If the function return is not WFS_SUCCESS, it is one of the following error conditions, indicating that the asynchronous operation was not initiated:

WFS_ERR_CONNECTION_LOST

The connection to the service is lost.

WFS_ERR_INTERNAL_ERROR

An internal inconsistency or other unexpected error occurred in the WOSA/XFS subsystem.

WFS_ERR_INVALID_HSERVICE

The hService parameter is not a valid service handle.

WFS_ERR_INVALID_HWND

The hWnd parameter is not a valid window handle.

WFS_ERR_INVALID_POINTER

A pointer parameter does not point to accessible memory.

WFS_ERR_NOT_STARTED

The application has not previously performed a successful WFSStartUp.

WFS_ERR_OP_IN_PROGRESS

A blocking operation is in progress on the thread; only WFSCancelBlockingCall and WFSIsBlocking are permitted at this time.

The following error conditions are returned via the asynchronous command completion message, as the hResult from the WFSRESULT structure:

WFS_ERR_CANCELED

The request was canceled by WFSCancelAsyncRequest.

WFS_ERR_INTERNAL_ERROR

An internal inconsistency or other unexpected error occurred in the WOSA/XFS subsystem.

WFS_ERR_NOT_LOCKED

The application requesting a service be unlocked had not previously performed a successful WFSLock or WFSAsyncLock.

See also WFSUnlock, WFSLock, WFSAsyncLock