3.2.4 Message Processing Events and Sequencing Rules
Depending on the protocol version and the operations that are requested by the client, clients MAY follow one or more of these protocol sequences:
Configure and activate resources and groups, as specified in section 126.96.36.199.
Clients MAY invoke protocol methods in any order, unless otherwise noted in the following subsections, and except where ordering is determined by RPC context-handling requirements (as specified in section 3.1). Upon successfully accepting the client request, the server MUST execute the method against the current configuration and state of the cluster.
Clients SHOULD implement reconnect-on-failure logic, as specified in section 3.2.1, by interpreting specific error codes that are returned by methods on either the client or server side of the RPC transport. Those error codes and the actions taken are as specified in section 188.8.131.52.
Except as specified in section 184.108.40.206, when a method completes, the values that are returned by RPC MUST be returned unmodified to the upper layer.
Except as specified in section 220.127.116.11, the client MUST ignore errors that are returned from the RPC server and notify the application invoker of the error received in the higher layer.
Clients SHOULD close context handles as specified in section 18.104.22.168.
Clients SHOULD maintain a client-side notification queue for each notification port as specified in sections 22.214.171.124 and 126.96.36.199.