[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-msg] Comments on the 1.09 about MessageOrder
Are there any alternative reliable messaging protocols other than ebXML RM? If so, we would need bindings for them. Maybe some day, HTTPR when it becomes a standard. Regards, Marty ************************************************************************************* Martin W. Sachs IBM T. J. Watson Research Center P. O. B. 704 Yorktown Hts, NY 10598 914-784-7287; IBM tie line 863-7287 Notes address: Martin W Sachs/Watson/IBM Internet address: mwsachs @ us.ibm.com ************************************************************************************* David Fischer <david@drummondgroup.com> on 12/05/2001 12:09:57 AM To: SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com>, ebxml-msg@lists.oasis-open.org cc: Subject: RE: [ebxml-msg] Comments on the 1.09 about MessageOrder Has this been decided? Are we going to allow only ebXML RM for MessageOrder? David. -----Original Message----- From: SHIMAMURA Masayoshi [mailto:shima.masa@jp.fujitsu.com] Sent: Thursday, November 29, 2001 3:26 AM To: ebxml-msg@lists.oasis-open.org Subject: [ebxml-msg] Comments on the 1.09 about MessageOrder Please change section 10 as following: P. 49, Line 1993-1994. It is highly RECOMMENDED that Reliable Messaging be used when a MessageOrder element is present. | V Reliable Messaging MUST be used when a MessageOrder element is present. P. 49, Line 1997. SHOULD | V MUST P. 49, Line 2009. The MessageOrder element MUST be used with the duplicateElimination attribute set to true. | V The MessageOrder element MUST be used with delivery behavior of Once-and-Only-Once. The Once-and-Only-Once delivery behavior means that duplicateElimination set to true and AckRequested element appears in messages, or duplicateElimination set to true and Acknowledgement element appears in messages. P. 49, Line 2021. only when duplicateElimination is true. | V only when delivery behavior is Once-and-Only-Once. P. 49, Line 2023. If duplicateElimination is not true | V If delivery behavior is not Once-and-Only-Once P. 49, 2025-2026 that have a duplicateElimination attribute with a value of true | V that have delivery behavior is Once-and-Only-Once P. 50, Line 2044 and 2046. when duplicateElimination has a value of true | V when delivery behavior is Once-and-Only-Once P. 50, Line 2050 and 2052. When duplicateElimination is true | V When delivery behavior is Once-and-Only-Once Because guarantee of message order can be realized only when delivery behavior is Once-and-Only-Once. Actually in the Message Service specification V1.0, guarantee of message order can be specified only when delivery behavior is Once-and-Only-Once. Please consider following case: MessageOrderSemantics: Guarantee Delivery behavior: At-Most-Once (duplicateElimination is true and AckRequired is not used). +----------+ ---- Message (SN=1)---> |receiving | ---- Message (SN=2)---> | MSH | ---- Message (SN=4)---> | | +----------+ In this case, receiving MSH is not sure that the Message of SN 3 will reach after that. It might never reach forever. It means that receiving MSH can't decide that when the Message of SN 4 should be passed to application. Regards, -- SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com> TEL:+81-45-476-4590(ext.7128-4241) FAX:+81-45-476-4726(ext.7128-6783) Planning Dep., Strategic Planning Div., Software Group, FUJITSU LIMITED ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC