IMsgrLock::SendResponse Method

Deprecated. Sends authentication data from a Messenger client to a Messenger service.


HRESULT SendResponse(      
    BSTR bstrAppStrId,
    BSTR bstrResponse,
    long lCookie


  • bstrAppStrId
    [in] BSTR that identifies the application's ID.
  • bstrResponse
    [in] BSTR that has been generated by an RSA-MD5 Message Digest Algorithm (MD5). See Remarks for more information.
  • lCookie
    [in] LONG that identifies the transaction session.

Return Value

Returns one of the following values:

S_OK The response was sent successfully.
E_FAIL The response has failed due to a catastrophic error.
E_INVALIDARG One of the parameters passed to the method was not valid.
MSGR_E_API_NOTINITIALIZED The Messenger client lock and key mechanism is not initialized.
MSGR_E_API_LOCKED The Messenger service API is locked.
MSGR_E_API_PENDING_UNLOCK The application timed out while waiting for the result of the challenge.
MSGR_E_API_UNLOCK_FAILED The application response to the challenge failed.
MSGR_E_API_ALREADY_UNLOCKED The Messenger service API is already unlocked.


The DMessengerPrivateEvents::OnLockChallenge event is fired when a Messenger service responds to a Messenger client request challenge. This event returns two parameters. The first parameter is a LONG that identifies a cookie. This cookie is passed to the Messenger service when the Messenger client initiates a challenge request with the IMsgrLock::RequestChallenge method. The second parameter is a BSTR, which is generated by the Messenger service. For more information, see the overview on the Messenger Lock and Key API.

Important  IMsgrLock::SendResponse is no longer available in Windows Vista. See Windows Messenger for more information.

See Also

IMsgrLock::RequestChallenge, DMessengerPrivateEvents::OnLockChallenge, Messenger Session Invite and Messenger Private APIs