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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

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

Subject: Re: delivery failure


In the current version of the spec the separation between MSH and the
application is somewhat blurred. There is no well defined interaction model
between the "application" and MSH, only an indication of what information would
come the application and what would be supplied by the MSH and some identified
"duties" and responsibilities of the MSH. We need to build on the figure 6-1 and
define the interaction model more comprehensively (a la MTA and MUA in the email
world). Otherwise, we will keep running into this kind of issue in many places..

Regards, Prasad

-------- Original Message --------
Subject: RE: delivery failure
Date: Thu, 19 Jul 2001 12:36:02 -0700
From: "Burdett, David" <david.burdett@commerceone.com>
To: "'HUGHES,JIM (HP-Cupertino,ex1)'" <jim_hughes@hp.com>,Martin W Sachs
CC: ebxml-msg@lists.oasis-open.org

I agree with Jim, the MSH would notify the calling application of the failed
message delivery using the Service Interface spec which is not yet
developed. I think the word SHOULD was used rather than MUST since:
1. the sending application may have no mechanism by which it can be notified
of failed delivery, or
2. the sending application may not care if the message was delivered

Basically this section is describing recommended behavior of the MSH which
cannot ever be independently verified.


-----Original Message-----
From: HUGHES,JIM (HP-Cupertino,ex1) [mailto:jim_hughes@hp.com]
Sent: Thursday, July 19, 2001 9:09 AM
To: Martin W Sachs
Cc: ebxml-msg@lists.oasis-open.org
Subject: RE: delivery failure

Marty -

This is one of the general topics discussed in the OASIS TC meeting this
week -- the Service Interface between the sending/receiving application and
its MSH. No conclusions reached other than this is a major piece of work
needed for the next version of the spec... and required for portability if
we expect applications to move between different MSH implementations.


> -----Original Message-----
> From: Martin W Sachs [mailto:mwsachs@us.ibm.com]
> Sent: Thursday, July 19, 2001 7:41 AM
> To: ebxml-msg@lists.oasis-open.org
> Subject: delivery failure
> How is a sending application informed of a delivery failure  in the reliable
> messaging function?  Is it one of the SOAP faults?
> 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
> **************************************************************

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

Powered by eList eXpress LLC