David, I guess you think that: Check of duplicate message is prerequisite condition for guarantee of message order. Thus if conversation is scope of guarantee of message order, all the received message's information (MessageId, etc.) in the conversation must be preserved in the Receiving MSH's persistent storage for duplication check until the conversation finishes. But actually, the Receiving MSH can remove received message's information when the message is passed to higher layer (application or middleware) in order and the passed message's persistDuration expires, except for the last received message in order. Because when a message's persistDuration expires, the message is never re-sent to the Receiving MSH: 7.4.6 PersistDuration ... If the PersistDuration has passed since the message was first sent, a Sending MSH SHOULD NOT resend a message with the same MessageId. (Line 1616-1617, P.39, V1.09) On Wed, 05 Dec 2001 14:27:31 -0600 David Fischer <
david@drummondgroup.com> wrote: > Oh wait! We can just use the reset feature after all the previous messages > pass persistDuration. If we do that, we don't need to keep the messages past > persistDuration. > > Regards, > > David. > >