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: RE: [ebxml-msg] Large file transmission using AS2 restart

I asked Terry Harding (author/editor) of the draft and he and I agree
that there is no obstacle in using the procedure with any HTTP POST
based protocol. There is a new HTTP header with an ID, and there is
state to retain on the receiver(and sender) side. The receiver also
needs to support the HEAD HTTP request. 

(It also pretends that a GET request on the resource URI exists and is
defined so that it would have a content-length associated with it that
the HEAD requests return. This content-length number allows the sender
to know where to restart, if necessary.)

Remember that the document is currently an Internet-Draft and not yet a

-----Original Message-----
From: Pim van der Eijk [mailto:pvde@sonnenglanz.net] 
Sent: Wednesday, March 24, 2010 7:52 AM
To: ebxml-msg@lists.oasis-open.org
Subject: [ebxml-msg] Large file transmission using AS2 restart


There is a requirement of some potential users of ebMS 3.0
to be able to exchange large files (Gigabytes and larger).
There is a specification for AS2 that offers a "restart"

We can borrow this feature for ebMS, and add a mini-section
to chapter 4 that references the AS2 feature. Since we just
reference the IETF RFC, this feature adds just a few lines
of text to the spec. Many multi-protocol B2B products
support this for AS2 already.  It would be minimal effort
for them to enable this for ebMS.  For ebMS users, it adds a
useful capability.  

As we did for pipelining, we could add a Pmode parameter to
indicate whether the ebMS MSH supports it or not.  If
"True", clients in HTTP client mode can add the HTTP ETAG
with ebMS messages sent and can use the HTTP HEAD command to
obtain the status of the transfer, as described in the RFC.
If "False", they should not do this. We've added Pipelining
to MEPBinding, and could do the same with "Restart":

PMode.MEPbinding.Restart  {True/False}

Or we could make it a parameter in PMode.Protocol

What do people think?   


To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

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