3.1.6 Other Local Events

Except as specified in the following paragraphs in this section, no local events are used on the server except the events that are maintained in the underlying RPC transport.

If the RPC connection fails, the server SHOULD free all context that is associated with the client. Such context MUST exist if any of the following has occurred:

  • The client has previously called ApiOpenCluster (section 3.1.4.1.1 for protocol version 2, or 3.1.4.2.1 for protocol version 3) or ApiOpenClusterEx (section 3.1.4.2.116 for protocol version 3) and not yet called ApiCloseCluster (section 3.1.4.1.2 for protocol version 2, or 3.1.4.2.2 for protocol version 3).

  • The client has previously called ApiOpenNode (section 3.1.4.1.67 for protocol version 2, or 3.1.4.2.67 for protocol version 3) or ApiOpenNodeEx (section 3.1.4.2.117 for protocol version 3) and not yet called ApiCloseNode (section 3.1.4.1.68 for protocol version 2, or 3.1.4.2.68 for protocol version 3).

  • The client has previously called ApiOpenResource (section 3.1.4.1.9 for protocol version 2, or 3.1.4.2.9 for protocol version 3), ApiOpenResourceEx (section 3.1.4.2.119 for protocol version 3), or ApiCreateResource (section 3.1.4.1.10 for protocol version 2, or 3.1.4.2.10 for protocol version 3) and not yet called ApiCloseResource (section 3.1.4.1.12 for protocol version 2, or 3.1.4.2.12 for protocol version 3).

  • The client has previously called ApiOpenGroup (section 3.1.4.1.42 for protocol version 2, or 3.1.4.2.42 for protocol version 3), ApiOpenGroupEx (section 3.1.4.2.118 for protocol version 3), or ApiCreateGroup (section 3.1.4.1.43 for protocol version 2, or 3.1.4.2.43 for protocol version 3) and not yet called ApiCloseGroup (section 3.1.4.1.45 for protocol version 2, or 3.1.4.2.45 for protocol version 3).

  • The client has previously called ApiGetRootKey (section 3.1.4.1.29 for protocol version 2, or 3.1.4.2.29 for protocol version 3), ApiCreateKey (section 3.1.4.1.30 for protocol version 2, or 3.1.4.2.30 for protocol version 3), or ApiOpenKey (section 3.1.4.1.31 for protocol version 2, or 3.1.4.2.31 for protocol version 3) and did not call ApiCloseKey (section 3.1.4.1.38 for protocol version 2, or 3.1.4.2.38 for protocol version 3).

  • The client has previously called ApiOpenNetInterface (section 3.1.4.1.92 for protocol version 2, or 3.1.4.2.92 for protocol version 3) or ApiOpenNetInterfaceEx (section 3.1.4.2.121 for protocol version 3) and not yet called ApiCloseNetInterface (section 3.1.4.1.93 for protocol version 2, or 3.1.4.2.93 for protocol version 3).

  • The client has previously called ApiOpenNetwork (section 3.1.4.1.81 for protocol version 2, or 3.1.4.2.81 for protocol version 3) or ApiOpenNetworkEx (section 3.1.4.2.120 for protocol version 3) and not yet called ApiCloseNetwork (section 3.1.4.1.82 for protocol version 2, or 3.1.4.2.82 for protocol version 3).

  • The client has previously called ApiCreateNotify (section 3.1.4.1.56 for protocol version 2, or 3.1.4.2.56 for protocol version 3) and not yet called ApiCloseNotify (section 3.1.4.1.57 for protocol version 2, or 3.1.4.2.57 for protocol version 3).

  • The client has previously called ApiCreateBatchPort (protocol version 3 only) and not yet called ApiCloseBatchPort (protocol version 3 only).

  • Note that additional context might exist due to pending operations or in progress operations.