RE: [ws-rx] AS need for ordered delivery?

["Duane Nickull" <dnickull@adobe.com>]

"There is a more relaxed and performant view, which allows streaming 
delivery: this says: nothing must be delivered to the application that 
is out of order (or a duplicate in case of EO delivery), even if not all

of the sequence has yet been received."

Alistair:

Is it reasonable for this TC to define a specific implementation
scenario for "in order delivery" and state it is applicable behind
service interfaces?  The opacity of service concept frees implementers
of each service to make those decisions and if this TC tries to reach
behind the service and mandate a specific implementation, I would
object.

Also - is it reasonable for an RMD to hold onto every single message
until it has received the entire sequence?  Why can't RMD deliver
message 1, 2 and 3 to the AD right away, then send a Nack back to the
RMS if 4 is missing and 5 comes next.   In this case, it could hold back
5 until 4 is present, but given that 1 and 5 may be some considerable
time apart this may itself be suboptimal.

Question for all:

Is it really the physical delivery or the ability to subsequently
understand the ordering of the messages that matters?

Duane