[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Agenda suggestion [was Phone call tomorrow (4 October)]
Peter and I want to propose the following in respect of your "3PC" discussion.
We are quite firmly opposed to modifying the fundamental process by
which the transaction outcome is decided. In other words we think that
2PC has the right number of messages to achieve a coordinated decision.
We agree with Mark Little on that point. However, we can see value in the
following, which may align with your concern:
Add a parameter to CONFIRMED called "report hazard [or whatever we called it on REQUEST_CONFIRM]" which can be T/F.If the Superior is prepared to take this hint (it need not do so), it will attempt to send a new message FINAL_OUTCOME with a contained HAZARD (if there was one), or with no contents (if the final outcome equalled the decided/intended outcome).
It is up to the Superior how this value is arrived at. Should the information reflect the state of the entire tree, or only the immediate Superior's branch? Should the Superior be allowed to ignore "unimportant" failures? That is a matter for the implementation/application configuration, and need not be dealt with in the spec.
We can certainly survey current issues (we will try to send a summary
out before the call).
Yours,
Alastair
Sazi Temel wrote:
Alastair,I would suggest we go over the current issues (if any) related to spec that Peter, Alex and you might bring before we discuss my suggestion. I think I have been pretty clear what I am suggesting and my position in my original e-mail and my reply to Mark Little. I would be happy to clarify any questions people might have.. and am ready to be convinced! In fact, I will respectfully accept not to discuss the issue at all if majority of people on call suggest so - assuming everybody had chance to read what has been suggested and Mark's comments.
Regards,
--SaziAt 07:06 PM 10/3/01 +0100, Alastair Green wrote:
Hi,Is anyone up for sponsoring the call tomorrow?
The 3PC issue could do with ventilation.
I have just spoken to Alex Ceponkus, who has emerged in Canada after a
longer removal than he anticipated, and I suspect his revision of the
messaging section is only just about to start, based on the results of
last week's meeting.Peter and I have been making significant if silent progress, and Mark
Little has fed in his parts. I expect that we will have a 0.8
(non-integrated with messaging) by this time next week.Yours,
Alastair
Sazi Temel
Principal Consultant,
eCommerce Services,bea Systems, inc. [www.bea.com]
begin:vcard n:Green;Alastair tel;cell:+44 795 841 2107 tel;fax:+44 207 670 1785 tel;work:+44 207 670 1780 x-mozilla-html:FALSE url:www.choreology.com org:Choreology Ltd version:2.1 email;internet:alastair.green@choreology.com title:Managing Director adr;quoted-printable:;;13 Austin Friars=0D=0A;London;;EC2N 2JX; fn:Alastair Green end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC