3.1.5.3 Receiving an EcDoAsyncWaitEx Method Call

The server SHOULD<15> support the EcDoAsyncWaitEx method call, as specified in [MS-OXCRPC] section 3.3.4.1.

Whenever an asynchronous EcDoAsyncWaitEx method call, as specified in [MS-OXCRPC] section 3.3.4.1, on the AsyncEMSMDB interface is received by the server, the server MUST validate that the asynchronous context handle provided is a valid asynchronous context handle that was returned from the EcDoAsyncConnectEx method call, as specified in [MS-OXCRPC] section 3.1.4.4. The server SHOULD NOT complete the call until there is a notification for the client session, or the call has been outstanding on the server 5 minutes. If the server already has a call outstanding for the same session context handle, the server SHOULD complete the new call and set the ErrorCode field to Rejected, as specified in [MS-OXCRPC] section 3.3.4.1, if another asynchronous RPC call is currently in progress on the server.

If the server completes the outstanding RPC call when there is a notification for the client session, the server MUST return the value NotificationPending in the pulFlagsOut field. The server MUST return 0x00000000 in the pulFlagsOut field if the call was completed when there is no notification for the client session.

Show: