ebxml-tp message


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

 


Help: OASIS Mailing Lists Help | MarkMail Help
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

Subject: no synch vs asynch indicator in CPP/CPA


With the removal of the BusinessProtocol and its children
from the tpaML 1.0.6 in our CPP/CPA DTD, we have lost the
ability to attribute synchronous versus asynchronous characteristics
of a delivery channel.

Presently, the BPM specifies synch versus asynch, but IMHO, this
is the WRONG place to specify such a thing as it imposes a
constraint on an implementation.

Rather, I think that a delivery channel and/or the
transport should be declared as having synch or asynch 
characteristics.

This is related to Dale's concerns and (hopefully) investigation
as to the capabilities of the sender which I believe
should also capture some aspect of the synch vs asynch nature
of the initiating (sending) Party's delivery channels.

The distinction as I see it is that the BP should be
independent of an implementation, but an implementation
that supports a BP would be engineered so as to provide for
either response pattern according to its needs.

Comments?

Cheers,

Chris
begin:vcard 
n:Ferris;Christopher 
tel;work:781-442-3063
x-mozilla-html:FALSE
org:Sun Microsystems, Inc;XML Technology Development
adr:;;One Network Drive;Burlington;Ma;01824-0903;USA
version:2.1
email;internet:chris.ferris@east.Sun.COM
title:Sr. Staff Engineer
x-mozilla-cpt:;0
fn:Christopher Ferris
end:vcard


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC