3.2.4 Message Processing Events and Sequencing Rules

  • Article

Upon the completion of the RPC method, the client MUST return the result unmodified to the higher layer. This is a stateless protocol with the exception of the NetrShareDelCommit method.

No sequence of method calls is imposed on this protocol, with the following exceptions:

  1. NetrShareDelCommit method: The first phase MUST be completed (by the NetrShareDelStart method) before the second phase is attempted.

  2. NetrFileGetInfo method: The NetrFileEnum method MUST be called to obtain the FileId before the NetrFileGetInfo method is called.

  3. NetrFileClose method: NetrFileEnum MUST be called to obtain the FileId before the NetrFileClose method is called.

When a method is completed, the values that the RPC returns MUST be returned unmodified to the upper layer.

The client MUST ignore errors returned from the RPC server and notify the application invoker about the error that was received in the higher layer. Otherwise, no special message processing is required on the client beyond the processing that is required in the underlying RPC protocol.