RE: Returning the whole message on Message Expiry Delivery Failures

[Marc Breissinger <marcb@webmethods.com>]

I agree.

marc

==========================================================================
Marc Breissinger                                   voice (W): 703-460-2504
Director, Product Strategy - webMethods, Inc.	   voice (C): 703-989-7689
Email:  marcb@webmethods.com                               We're Hiring!!!
Email2: breissim@earthlink.net                   http://www.webMethods.com
==========================================================================





-----Original Message-----
From: Burdett, David [mailto:david.burdett@commerceone.com]
Sent: Sunday, February 25, 2001 10: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