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] | [Elist Home]

Subject: RE: T2 Reliable Messaging w/o CPA or VIA...

Regarding persistDuration, the message service spec (line 1758-59) states
"If a message cannot be sent successfully before persistDuration has
passed, then the Sending MSH should report a delivery failure." Lines
1756-1757 also place some responsibility on the sending MSH.

The above statements mean that the persistDuration also applies to the
sending MSH and must be in the header. Or it could mean that it has to be
in the CPA (or whatever you want to use instead of a CPA), where it in fact
is, so that both parties agree on the value.



Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com

---------------------- Forwarded by Martin W Sachs/Watson/IBM on 07/30/2001
06:38 PM ---------------------------

"Burdett, David" <david.burdett@commerceone.com> on 07/30/2001 03:29:50 PM

To:   "'David Fischer'" <david@drummondgroup.com>
cc:   ebXML Msg <ebxml-msg@lists.oasis-open.org>
Subject:  RE: T2 Reliable Messaging w/o CPA or VIA...


Let's  take of these in turn ...

>>>This is the accuracy to which a recipient  of a message claims to keep
their internal system clocks. This should probably  be part of a CPP and
not vary from message to message therefore it does not need  to be in the

>>>This needs to be in the Via since it can vary on each hop of  a
multi-hop message. I suppose though that, if you are not doing multi-hop
then  it forces use of the Via element. I think we could either:
1. Put  reliableMessagingMethod in the main  MessageHeader with the copy in
the Via element over-riding it, or
2. Change  the definition of the Via element to suggest that it to be used
when there is no  intermediary

>>>This is in Via for the same reason as for  reliableMessagingMethod - it
can vary from hop-to-hop

retries& retryInterval
>>>These are both parameters that apply to the  sender of a message and
over which the receiver of message can have no effective  control. There is
therefore no need for them to be in the header. They should  however be in
the CPP for the sender

>>>PersistDuration only applies to the  recipient of a message as it
specifies the minimum time the recipient will keep  a message. The sender
cannot (should not?) control this, therefore there is no  need for it to go
in the header.

I'd  appreciate your thoughts.

-----Original Message-----
From: David Fischer  [mailto:david@drummondgroup.com]
Sent: Monday, July 23, 2001 7:07  PM
To: Burdett, David
Cc: ebXML Msg
Subject: T2  Reliable Messaging w/o CPA or VIA...

Section 10.2 (line 1695) says:

This  parameter information can be specified in the CPA or in the

But I can't find anywhere in  the MessageHeader to set the following


This seems like a formidable problem when  doing reliable messaging
(ackRequested) without an intermediary (no  Via).  If we put this
information back in the MessageHeader, why is  it also in the Via?  This
was in the MessageHeader in v0.91 but it was  taken out... probably
shouldn't have been.


David Fischer
Drummond  Group.

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

Powered by eList eXpress LLC