David, thanks for your comments, it brings us back to some of the "what's
the size of this hole?" issues we previously had with a few security issues.
In general, Marty is coming closest to saying "what's wrong with having the
application wait for an Acknowledgment message before sending another
message?" This seems to be a core issue: The Message Order module in MSH is
purely an efficiency mechanism. It doesn't add support for message ordering
to the infrastructure, it only makes multiple outstanding (un-acknowledged)
messages possible. How important is that efficiency?
Even if it is very important, we have a number of issues raised in this and
the related "... MessageOrder" thread indicating this module isn't fully
baked. I'd like to add an additional issue: A conversation seems to last
throughout the lifetime of a business process instance (one run through the
BPSS "script"). However, only a few points (if any) in that business
process are going to require explicit re-ordering of outstanding messages.
The scope of the sequence we've defined remains far too large.
thanx,
doug