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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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

Subject: Re: Ack Message Payload??

David put forth a discussion on implicit ACKs while we were in Dallas. The
idea was that a MessageType=Normal *could* be used as both a BP-level
response as well as an implicit ACK.

Some of us discussed this before, and I've expressed my stand that this is a
"VeryImportantPattern". We might call it "ImplicitAcknowledgement" Pattern,
but just for a short period (see David's post and my response on Multi-hop
RM). It looks like it is already in use by POC people for RR lookup. Using
"Normal" and "RefToMessageId" (you can use "ConversationId" on top of them
if you want) gives us not only a mechanism for "ImplicitAcknowledgement",
but also for "AsynchronousRPC" and for "LongCollaboration" Patterns.

We agreed to defer the discussion to phase II because it was felt that we
had our plate full and we couldn't easily get to consensus.

I hope we are not going to drop the ball on this one.

Regardless, I think that a BP-level ACK *should* have a payload, even if it
is a minimal one like:

I had thought of a possible solution when you might use "Normal" and
"ServiceInterface" and "Action" with an empty payload in order to
"BusinessAcknowledge", but I am not sure if that should be considered as a
kludge or not. Empty Business Payloads ("Normal") that DO Business stuff via
"ServiceInterface" and "Action" might not be that bad?

It SHALL have a MessageType="Normal" and it SHALL have a ServiceInterface
and Action appropriate to its purpose at least for the current state of

You have my FULL support on this one.


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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC