[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: interposition requirements
<<<<
Good point. We (the coordinator) just does not know what kind of infrastructure is behind the participants... it might or not be a good wish to have a flat transaction from the performance point of view. >>>> Exactly. It may want flat, but it can't rely upon it.
I think that even if the participant can support flat (and lets face it, all of them will), if it supports interposition and the service has been (locally) configured accordingly, it should be able to ignore flatness. The initiator only has a small part of the whole picture and can't/shouldn't look into my (as an implementer) domain and tell me what kind of protocol to allow. Mark.
----------------------------------------------
Dr. Mark Little (mark@arjuna.com) Transactions Architect, HP Arjuna Labs Phone +44 191 2064538 Fax +44 191 2064203 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC