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] Issue for your review
Title: RE: [ebxml-msg] Issue for your review
>For example, using SMTP a call into the SMTP server to pass the
>data and be able to return from the call means the message is dispatched.
>It may not have gone out or delivered to the destination but from
>the MSH level the message is "dispatched". This is similar for JMS -
>once you return from the call to the server the message is "dispatched".
>For HTTP, dispatched means you get a 2xx back. This is required
>by the HTTP trasport.
>
>Note that "dispatched" does not necessary mean delivered. Some
>transport means Yes, e.g. HTTP, some means May Be, e.g. SMTP.
>
>For the spec if it can define what it means by "dispatched" and
>give examples in relation to well know transport protocols such as
>HTTP, SMTP, JMS, FTP then these can be used as guides for other
>protocols.
Abstract discussion of how the ebXML message data is handed-off
from sending MSH to its transport layer is a good idea. This is
the scope of dispatching mechanism I believe that is pertinent.
Mapping that abstraction to a particular transport protocol (JMS,
HTTP/S, FTP, SMTP, etc.) would be a good idea as well. Should
such transport protocol specific discussion be normative or it
belongs on a best practice document?
thanks,
Zahid