NdisMCmDropPartyComplete returns the final status of a client's request, for which the MCM driver previously returned NDIS_STATUS_PENDING, to remove a party from a multipoint VC.
void NdisMCmDropPartyComplete( _S_, _H_ );
Specifies the final status of the requested operation, either NDIS_STATUS_SUCCESS or any caller-determined NDIS_STATUS_ XXX except NDIS_STATUS_PENDING.
Specifies the handle to the party that the client requested be dropped. The MCM driver obtained this handle from its per-party state area designated by CallMgrPartyContext that was passed as an input parameter to its ProtocolCmDropParty function.
An MCM driver must call NdisMCmDropPartyComplete if its ProtocolCmDropParty function previously returned NDIS_STATUS_PENDING for the given NdisPartyHandle . Neither NDIS nor the client, which initiated the pended drop-party operation with a call to NdisClDropParty, can release the resources they allocated to maintain per-party state until the MCM driver's call to NdisMCmDropPartyComplete causes a call to that client's ProtocolClDropPartyComplete function.
If it passes NDIS_STATUS_SUCCESS for the Status, the MCM driver must consider the NdisPartyHandle invalid when NdisMCmDropPartyComplete returns control. The MCM driver can release (or reinitialize for reuse) any resources that it allocated to maintain state for this party after NdisMCmDropPartyComplete returns control.
Only connection-oriented miniport drivers that provide integrated call-management support can call NdisMCmDropPartyComplete. Stand-alone call managers, which register themselves with NDIS as protocol drivers, call NdisCmDropPartyComplete instead.
|Minimum supported client||Supported for NDIS 6.0 and NDIS 5.1 drivers (see NdisMCmDropPartyComplete (NDIS 5.1)) in Windows Vista. Supported for NDIS 5.1 drivers (see NdisMCmDropPartyComplete (NDIS 5.1)) in Windows XP.|
|Header||ndis.h (include Ndis.h)|
|DDI compliance rules||Irql_MCM_Function|