3.2.4.8.2 Reading the Version 2 Notification Port Event Queue

The client-side queue of events specified in section 3.2.1.1.1 holds event indications returned by the ApiGetNotifyV2 method (section 3.1.4.2.138 for protocol version 3). It also holds the following events generated by the client:

  • CLUSTER_CHANGE_CLUSTER_STATE_V2, as specified in section 3.2.4.6.

  • CLUSTER_CHANGE_CLUSTER_RECONNECT_V2, as specified in section 3.2.4.6.

  • CLUSTER_CHANGE_CLUSTER_HANDLE_CLOSE_V2, as specified in section 3.2.4.7.

  • CLUSTER_CHANGE_RESOURCE_HANDLE_CLOSE_V2, as specified in section 3.2.4.7.

  • CLUSTER_CHANGE_GROUP_HANDLE_CLOSE_V2, as specified in section 3.2.4.7.

  • CLUSTER_CHANGE_NETWORK_HANDLE_CLOSE_V2, as specified in section 3.2.4.7.

  • CLUSTER_CHANGE_NETINTERFACE_HANDLE_CLOSE_V2, as specified in section 3.2.4.7.

  • CLUSTER_CHANGE_NODE_HANDLE_CLOSE_V2, as specified in section 3.2.4.7.

  • CLUSTER_CHANGE_REGISTRY_HANDLE_CLOSE_V2, as specified in section 3.2.4.7.

When a client application requests an event from a particular notification port, the client SHOULD remove the next entry from the client-side queue associated with that notification port and return the notification event information to the application as specified in section 3.1.4.2.138.

In response to the event identifier CLUSTER_CHANGE_CLUSTER_STATE_V2, an application typically cleans up any client-side state associated with the protocol session.

In response to the following event identifiers:

  • CLUSTER_CHANGE_CLUSTER_HANDLE_CLOSE_V2

  • CLUSTER_CHANGE_RESOURCE_HANDLE_CLOSE_V2

  • CLUSTER_CHANGE_GROUP_HANDLE_CLOSE_V2

  • CLUSTER_CHANGE_NETWORK_HANDLE_CLOSE_V2

  • CLUSTER_CHANGE_NETINTERFACE_HANDLE_CLOSE_V2

  • CLUSER_CHANGE_NODE_HANDLE_CLOSE_V2

  • CLUSTER_CHANGE_REGISTRY_HANDLE_CLOSE_V2

An application typically unblocks and closes the notification port as specified in section 3.2.4.5, if there are no remaining open context handles that were previously registered with the notification port, as specified in ApiAddNotifyV2 (section 3.1.4.2.137) for protocol version 3. All other event identifiers are informative to the application and suggest no particular action on the part of the client or application part.