22.214.171.124.1 Version 1 Notification Ports
To create a version 1 notification port, the client SHOULD call ApiCreateNotify (section 126.96.36.199.56) for protocol version 2, or section 188.8.131.52.56 for protocol version 3) to obtain an HNOTIFY_RPC context handle. Upon successful completion of ApiCreateNotify, the client SHOULD create a client-side queue associated with the notification port, as described in section 184.108.40.206, to hold event indications later received using the ApiGetNotify method (protocol version 2 or protocol version 3) as well as CLUSTER_CHANGE_CLUSTER_STATE, CLUSTER_CHANGE_CLUSTER_RECONNECT, and CLUSTER_CHANGE_HANDLE_CLOSE event indications. No event indications are queued by the server to the notification port until an event filter with an optional target cluster object has been registered with the port.
After the port is opened, the client MAY register an event filter to instruct the server to begin queuing the respective event indications on the port. The following methods are used to register the event filters:
After the first event filter is registered, the client SHOULD call ApiGetNotify to begin receiving event indications that are queued to the port. The client MAY continue to register additional event filters as necessary.
When a client has finished performing operations with an HNOTIFY_RPC context handle, it SHOULD unblock any outstanding ApiGetNotify calls by calling ApiUnblockGetNotifyCall (section 220.127.116.11.107) for protocol version 2, or section 18.104.22.168.107 for protocol version 3<152> and then release the context handle by calling ApiCloseNotify (section 22.214.171.124.57 for protocol version 2, or 126.96.36.199.57 for protocol version 3).