COM+ collects the vote and decides whether to commit or abort the transaction when the root object deactivates. If I, the root object, am happy and all other transaction participants are happy, then we have a party and the transaction commits. If one participant is unhappy, the transaction will not commit, even if I am happy. In the general 2 phase-commit scenario, no single particpant has complete control of the transaction outcome (that is the main rationale for using 2 phase-commit).

What you say is true in one special case though: I am the only participant in the transaction. In that case, you may state that you have control in the sense of decision control, because you are the only one voting. But in that case: why use 2-phase commit in the first place?

Kjell

>
> Sure you can control the transaction. If the root object
> deactivates with its happy _and_ done bit turned on, the
> transaction will commit. If the root object deactivates with
> its happy bit off and the done but turned on, you the
> transaction will be aborted.
>
> All of this can be controlled using the IContextState
> interface, and you can obtain a reference to the context by
> calling CoGetObjectContext.
>

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]