Date: Sun, 14 Oct 2001 22:37:02 -0400
From: Martin W Sachs <>
New MWS comment: I have never understood the value of
messageOrderSemantics, especially since ordering is performed separately
for each conversation.
I understand what you're saying here and you have an interesting point.
I checked this out with my colleague Mike Rowley, who says:
Not quite. Within a single collaboration, it is sometimes important that the
messaging system not reverse the order of messages. The BPSS may require, for
example, that an Invoice be sent and then an Advanced Shipment Notice (ASN),
in that order. Neither of these have response messages so they may be sent
one right after the other. The code on the other side will be written on the
assumption that the ASN will never arrive before the Invoice, so if the
messaging system gets them out of order, it will break the collaboration.
That is, the BPSS can specify a BinaryCollaboration that has two
BusinessTransactionActivities, one after the other in a particular
order, each one of them a BusinessTransaction specifying a document
flow consisting only of a "request".
