[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [business-transaction] Regarding issue #89
Peter
------------------------------------------
Peter
Furniss
Chief Scientist, Choreology Ltd
web: http://www.choreology.com
email:
peter.furniss@choreology.com
phone: +44 20 7670 1679
direct: +44 20
7670 1783
mobile: +44 7951 536168
13 Austin Friars, London EC2N 2JX
-----Original Message-----
From: WEBBER,JIM (HP-UnitedKingdom,ex1) [mailto:jim_webber@hp.com]
Sent: 24 April 2002 09:56
To: business-transaction@lists.oasis-open.org
Subject: RE: [business-transaction] Regarding issue #89Hello TC,e) I disagree with the idea that this will not have any impact on protocol as it stands now. How would one externalize the state without involving the BTP actors? We cannot just say it will not have impact on BTP. Surely some actors/roles will involve in externalizing the state and its consistency, perhaps even the participants will involve... If you can do it without involving the BTP actors and without changing any aspects of the protocol, then it is clear that the externalizing state is out of scope of BTP work - there is nothing to do other than agreeing on a form that we think that a BTP system will externalize its state. Even if so, I do not see its urgency at this version of the spec. If there is no impact, and no changes needed, perhaps I am also missing something here...
I think Sazi has hit the nail on the head here. If we are to allow externalisable state, the there will be one more role in BTP multiplied by however many actors can play that role. Would this not therefore necessitate considerable changes?However, I could still happily be convinced of the viability of this with a suitable use-case.Also, I am not using the "royal we" here since there has been far too much of that on these lists lately ;-)Jim
Attachment:
Issue 89 scope.doc
Description: MS-Word document
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC