[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: T2 Reliable Messaging w/o CPA or VIA...
mshTimeAccuracy
>>>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 MessageHeader
reliableMessagingMethod
>>>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
Thoughts?
I'd appreciate your thoughts.
David
-----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 MessageHeader
But I can't find anywhere in the MessageHeader to set the following parameters:mshTimeAccuracy
reliableMessagingMethod
ackRequested
retries
retryInterval
persistDurationThis 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.
Regards,
David Fischer
Drummond Group.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC