ebxml-msg — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [ebxml-msg] Arvola's SyncReply issues
MHonArc v2.5.2 -->ebxml-msg message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ebxml-msg] Arvola's SyncReply issues
- From: Arvola Chan <[email protected]>
- To: Doug Bunting <[email protected]>, ebXML Msg <[email protected]>
- Date: Thu, 03 Jan 2002 14:06:41 -0800
|
Doug:
I believe it was in the joint MSG/CPPA meeting in
October in Palo Alto that we decided that the 1.1 CPP/A spec would not
explicitly address the issue of intermediaries, and that the use of
intermediaries would have to be configured through other means for
now.
If the sender asks for a synchronous reply as well
as an intermediate Acknowledgment, as opposed to an end-to-end Acknowledgment,
one possibility is for the intermediary to withhold the
intermediate Acknowledgment until it has gotten the response (from the next
intermediary or from the To Party MSH), and then piggyback its intermediate
Acknowledgment on the response message. In this case, the sender still only
receives a single synchronous response as opposed to an intermediate
Acknowledgment and a response as separate messages. If we decide to do this,
some changes to section 11 may be necessary.
On point (12) below, I did mention
I think there are actually four aspects of
reliable messaging behavior: (1) persisting the sent message and retry
on the part of the sender when an Acknowledgment is not returned in
time;
Thanks,
-Arvola
|