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] | [List Home]

Subject: Groups - Message Splitting and Joining Protocol Proposal (Message Splitting.odt) uploaded

Here is a proposal alternative to AS2-Restart for large message handling. 
It introduces a SOAP-based splitting/joining protocol that composes with

 -- Mr. Pim van der Eijk

The document named Message Splitting and Joining Protocol Proposal (Message
Splitting.odt) has been submitted by Mr. Pim van der Eijk to the OASIS
ebXML Messaging Services TC document repository.

Document Description:
This chapter specifies a protocol for transmitting a large SOAP-rooted,
MIME Multipart/Related envelope (SWA and MTOM) message as a series of SOAP
message fragments. The protocol composes with other SOAP protocols
security, addressing, reliable messaging and ebMS. An implementation of the
protocol operates as a discrete module in a SOAP processing pipeline. The
protocol defines how a sending MSH can split a message in fragments and a
receiving MSH can reassemble it from its fragments in an interoperable
While the protocol can be used with other Web Services profiles, its main
goal is to support transfer of large ebMS messages. The main benefits of
the protocol in that context are:
Support for both push and pull message exchange (whereas the AS2 restart
feature is limited to push exchanges);
Reliable messaging is leveraged to transmit (and, if needed, retransmit)
The upper bound of the delays caused by a using store-and-forward
intermediary and the temporary storage space needed by such an intermediary
are proportional to the fragment size, rather than to the message size. 
Fragments can be routed individually through a multi-hop network. Fragments
may follow different paths from sender to recipient. If one intermediary
fails and traffic is re-routed via an alternative route, only the
undelivered fragments need to be resent.
The (optional) compression feature applies to the entire MIME envelope
(rather than individual payloads, as in the AS4 compression feature) and
includes the SOAP header.
The protocol composes with the ebMS message bundling feature.

View Document Details:

Download Document:  

PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration

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