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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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


Subject: RE: Returning the whole message on Message Expiry Delivery Failures


I agree with you on this one David.  In fact, I think that I have only
seen one message against this change.

Ralph Berwanger

-----Original Message-----
From: Burdett, David [mailto:david.burdett@commerceone.com]
Sent: Sunday, February 25, 2001 9:42 PM
To: ebXML Transport (E-mail)
Subject: Returning the whole message on Message Expiry Delivery Failures


Folks

Section 10.2.3 (TimeToLive) says that if TimeToLive is expired, then the
"DeliveryFailure" error message should return a payload of the ebXML
message
that has expired. I disagree with this in that this is the only error
that
requires the return of the message in error and also, the message could
be
huge (many 100s of Mb) when requiring the sending of all of it would not
make sense. I propose that this requirement is removed. The
RefToMessageId,
alone should be sufficient.

Thoughts?

David

Solution Strategy, Commerce One
4400 Rosewood Drive, Pleasanton, CA 94588, USA
Tel/VMail: +1 (925) 520 4422; Cell: +1 (925) 216 7704; Pager: +1 (888)
936
9599 
mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org

------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org


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

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC