RE: [ebxml-msg] Groups - Initial thought draft Large Paylod handling (Largepayloadsupport.htm) uploaded

["Pim van der Eijk" <pvde@sonnenglanz.net>]

Hello Ian,

I've borrowed some of the ideas in your initial proposal in
the draft I just uploaded.
Looking forward to your comments.

Pim

-----Original Message-----
From: Pim van der Eijk [mailto:pvde@sonnenglanz.net] 
Sent: 19 January 2010 21:49
To: ian.c.jones@bt.com; ebxml-msg@lists.oasis-open.org
Subject: RE: [ebxml-msg] Groups - Initial thought draft
Large Paylod handling (Largepayloadsupport.htm) uploaded

 

A separate question to discuss:

The AS4 draft defines a compressed payload option.  This
does not provide all the functionality of the "payload
fragmentation" protocol described in Ian's message
(referenced below).  Compressing individual payloads does
not help with messages that have large payloads that are
already compressed (e.g. PDF documents or ZIP archives), are
very large even after compression (e.g. medical images, data
cubes, a day's worth of billing data from a telco etc.), and
messages with many payloads (none of which are too large,
but the result is a very large message).  

In a multi-hop environment, splitting large messages and
sending them separately is also preferable to storing and
forwarding large messages as atomic units.  If they are
split, an intermediary can forward each part immediately
after it is received, without having to wait for the other
units.  With very large messages, storing and forwarding can
introduce an unacceptable delay.  With end-to-end
reliability, only message fragments that fail need to be
resent.

Many enterprise messaging products have limits on message
size and automatically split and send individually messages
that exceed message sizes.  Since we already have bundling
in part 2, I think we should consider a fragmenting protocol
too.

Messages bundles may be large. Fragmenting and bundling
could be composable.  Bundle two user messages, one with a
99 MB payload, one with a 1 M payload. Then fragment into 20
5 MB parts for efficient transmission through an icloud.

Pim


-----Original Message-----
From: ian.c.jones@bt.com [mailto:ian.c.jones@bt.com]
Sent: 31 October 2007 21:59
To: ebxml-msg@lists.oasis-open.org
Subject: [ebxml-msg] Groups - Initial thought draft Large
Paylod handling (Largepayloadsupport.htm) uploaded

The document named Initial thought draft Large Paylod
handling
(Largepayloadsupport.htm) has been submitted by Mr Ian Jones
to the OASIS ebXML Messaging Services TC document
repository.

Document Description:
This is an intial thought draft of the large payload
handling module for part 2 based on the work at the
September 2007 Face to Face

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/docum
ent.php?document_id=25928

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/downl
oad.php/25928/Largepayloadsupport.htm


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


------------------------------------------------------------
---------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_work
groups.php