MHonArc v2.5.2 -->
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...
Title:
David
Let's
take of these in turn ...
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?
ackRequested
>>>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
>>>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.
David