Re: [ebxml-msg] Re: Comments on the 1.09 about ConversationId

[Dan Weinreb <dlw@exceloncorp.com>]

   Date: Mon, 03 Dec 2001 20:30:08 -0600
   From: David Fischer <david@drummondgroup.com>

									 If there
   are no messages in the persistent store pertaining to a conversation, then there
   is no need to store it any longer for the purposes of maintaining message order.

I'm not sure that would work.  Suppose two parties establish a
conversation with ID 5551212.  Party A sends messages numbered 1
through 10 to Party B, and party B's application reads all the
messages and acknowledges them, so that there aren't any messages
still waiting to be delivered to B.  Now a message arrives at B with
conversation ID 5551212 and a sequence number of 12.  The MSH at B's
end has to realize that is should not deliver this message to the
application because message 11 hasn't arrived yet.  So the MSH at B's
end has to be storing somewhere the fact that the most recent message
delivered to the application from conversation 5551212 is 10.

-- Dan