[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: terminology
I think coordinator is overloaded, and as I
said before, if we are allowing traditional transaction systems to be used in
conjunction with BTP then there's already two types of coordinator to
differentiate. I'd like to have a term that's not used in TP at the very
least.
I don't think we should use the term
transaction at all in any term. In this field, transaction == ACID transaction.
In addition, "lightweight" is very subjective. Other terms I could think of:
collective, cohort, union?
We (HP) are working on putting together the Use Case section of the
document. I'm still waiting for offers from someone to do the same for the
terminology and other sections. I'll send out another email today asking
again.
Cheers,
Mark.
-----------------------------------------------------------------------
SENDER : Dr. Mark Little, Architect (Transactions), HP Arjuna Labs PHONE : +44 191 206 4538, FAX : +44 207 670 1964 EMAIL : mark@arjuna.com |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC