[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Returning the whole message on Message Expiry Delivery Failur es
I also support the motion. David -----Original Message----- From: Doug Bunting [mailto:Doug@ariba.com] Sent: Thursday, March 01, 2001 11:27 AM To: 'Marc Breissinger'; david@drummondgroup.com; Burdett, David; ebXML Transport (E-mail) Subject: RE: Returning the whole message on Message Expiry Delivery Failur es I second the motion. -----Original Message----- From: Marc Breissinger [mailto:marcb@webmethods.com] Sent: March 1, 2001 10:39 To: david@drummondgroup.com; Burdett, David; ebXML Transport (E-mail) Subject: RE: Returning the whole message on Message Expiry Delivery Failures I propose the following wording: If the TO Party's MSH receives a message where TimeToLive has expired, it SHALL send a message to the From party MSH, reporting that the TimeToLive of the message has expired. This message SHALL contain an Error in the ErrorList that has the errorCode attribute set to TimeToLiveExpired, and the severity attribute set to Error. Simply don't mention anything about the expired payload at all. 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: David Fischer [mailto:david@drummondgroup.com] Sent: Thursday, March 01, 2001 9:37 AM To: Burdett, David; ebXML Transport (E-mail) Subject: RE: Returning the whole message on Message Expiry Delivery Failures So should returning the message be OPTIONAL or MUST NOT? David Fischer Drummond Group. BTW David, you have a note at the beginning of the References which says: <DB>What's the difference between normative and non-normative</DB> My definition of "normative" is "what ought to be" so the normative references would be non-standards we want to reference because we think they ought to be. (CPA should probably be in here somewhere). However, this is not how things are arranged so I need to be stupid and ask: What is the difference between Normative and Non-Normative? -----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 ------------------------------------------------------------------ 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 ------------------------------------------------------------------ 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]
Powered by eList eXpress LLC