MHonArc v2.5.2 -->
















ebxml-msg message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]








Subject: [ebxml-msg] RE: Public usage scenario documents




From: Martin W Sachs <mwsachs@us.ibm.com>
To: Tony Fletcher <tony.fletcher@choreology.com>
Date: Tue, 28 May 2002 08:18:57 -0400







Tony,

In other words, you are saying: ignore ebXML reliable messaging and use
BTP.  Even if a consensus agrees with you, the MSG spec needs at least a
surgeon general's warning that reliable messaging may fail to be reliable
under system-failure conditions.

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
*************************************************************************************


                                                                                                                               
                      "Tony Fletcher"                                                                                          
                      <tony.fletcher@chor        To:       Martin W Sachs/Watson/IBM@IBMUS, "Cutler, Roger \(RogerCutler\)"    
                      eology.com>                 <RogerCutler@chevrontexaco.com>                                              
                                                 cc:       "Christopher Ferris" <chris.ferris@sun.com>, "'Duane Nickull'"      
                      05/28/2002 04:55 AM         <duane@xmlglobal.com>, "eBTWG List" <ebtwg@lists.ebtwg.org>, "'bhaugen'"     
                                                  <linkage@interaccess.com>, "Randy Clark" <Randy.Clark@bakerhughes.com>,      
                                                  "Cutler, Roger \(RogerCutler\)" <RogerCutler@chevrontexaco.com>,             
                                                  <ebxml-msg@lists.oasis-open.org>                                             
                                                 Subject:  RE: Public usage scenario documents                                 
                                                                                                                               
                                                                                                                               
                                                                                                                               



Dear Roger, Marty, Duane and others,

Another possibility is to use the Business Transaction Protocol (BTP - now
an OASIS Technical Committee specification)  to 'wrap' the messaging (then
can use straight forward ebXML messaging - do not really need reliable
messaging but could be used as belt and braces).  My understanding is that
using BTP around an application message can give each side assurance that
the message was received, or both sides know that something went wrong.  Of
course, you do not get something for nothing.  The BTP engines on both
sides
must be implemented correctly and each side has to take a persistent log so
that the loss of the last message problem Roger raises is detected and can
be recovered from.  BTP engines will be available as packages that can be
easily 'slotted' into systems.

Best Regards     Tony
A M Fletcher
Choreology Ltd., 13 Austin Friars, London EC2N 2JX     UK
Tel: +44 (0) 20 76701787         Mobile: +44 (0) 7801 948219
tony.fletcher@choreology.com <mailto:tony.fletcher@choreology.com>
(Home: amfletcher@iee.org)