Rediger

Del via

Network Module Detachment

  • Artikkel

An attached pair of network modules are detached from each other when either the client module or the provider module deregisters with the Network Module Registrar (NMR). A client module deregisters with the NMR by calling the NmrDeregisterClient function and a provider module deregisters with the NMR by calling the NmrDeregisterProvider function. The following diagram illustrates the network modules initiating deregistration.

Diagram showing network modules initiating deregistration process.

When either network module deregisters with the NMR, the NMR calls both the client module's ClientDetachProvider callback function and the provider module's ProviderDetachClient callback function to initiate detaching the network module. The following diagram illustrates the NMR initiating the detachment.

Diagram showing NMR initiating the detachment of network modules.

If the client module is unable to detach itself from the provider module immediately, it calls the NmrClientDetachProviderComplete function after it completes detaching itself from the provider module. Likewise, if the provider module cannot detach itself from the client module immediately, it calls the NmrProviderDetachClientComplete function after it completes detaching itself from the client module. The following diagram illustrates the network modules completing the detachment.

Diagram depicting network modules completing the detachment process.

After both the client module and the provider module have completed detachment from each other, the NMR calls the client module's ClientCleanupBindingContext callback function and the provider module's ProviderCleanupBindingContext callback function so that the network modules can clean up their respective binding contexts for the attachment. The following diagram illustrates the NMR initiating cleanup.

Diagram displaying NMR initiating cleanup after network modules detachment.

If the client module deregistered with the NMR, the deregistration of the client module is not complete until the client module has completely detached from all of the provider modules that it was previously attached to and all of those provider modules have completely detached from the client module. The client module waits for the deregistration to complete by calling the NmrWaitForClientDeregisterComplete function. Likewise, if the provider module deregistered with the NMR, the deregistration of the provider module is not complete until the provider module has completely detached from all of the client modules that it was previously attached to and all of those client modules have completely detached from the provider module. The provider module waits for the deregistration to complete by calling the NmrWaitForProviderDeregisterComplete function. The following diagram illustrates the network modules waiting for deregistration to complete.

Diagram showing network modules waiting for deregistration completion.