3.2.2.4 Message Processing Events and Sequencing Rules

This protocol MUST direct the RPC ([MS-RPCE] section 3) runtime to do the following:

  • Perform a strict NDR data consistency check at target level 6.0.

  • Reject a NULL unique or full pointer with a non-zero conforming value.

Clients MUST manage registrations throughout their lifetimes. Specifically, clients MUST call IRPCAsyncNotify_UnregisterClient for each successful call to IRPCAsyncNotify_RegisterClient.

When either IRPCAsyncNotify_GetNewChannel or IRPCAsyncNotify_GetNotification returns with a success code, the client SHOULD issue the next call of the same kind as soon as possible in order to minimize the amount of buffering and risk of event loss on the server.

The syntax and behavior for the methods of the IRPCAsyncNotify interface are fully specified in section 3.1.1.4.