OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

business-transaction message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: [business-transaction] issue on participant and serviceidentification


 
Mark, Peter,

In general I think a very simple view could be taken of the relationship between application messages and associated BTP messages.

Abstractly: BTP messages can be associated with application messages. The meaning of any such association is determined by cooperation between the application senders and receivers, and is outwith the scope of the BTP specification.

Binding proforma (rules): a binding may specify how BTP messages are associated to application messages [and it therefore may not]. 

Concrete example: SOAP/HTTP/XML binding states that a <btp:messages> when present in the SOAP header is associated with the content of the SOAP body.

OK, but how does this address this problem of identifying participants at termination time?
 
Mark.
 
----------------------------------------------
Dr. Mark Little, Distinguished Engineer,
Transactions Architect, HP Arjuna Labs
Email: mark_little@hp.com
Phone: +44 191 2606216
Fax  : +44 191 2606250
 
 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC