Implementation question for RM spec!

["Patil, Sanjay" <Spatil@netfish.com>]

I was going through the Reliable Messaging spec for scoping the work
involved in implementing the spec for the upcoming Tokyo POC.
Questions about the same ...particularly in the context of the following
requirement posed by the RM spec ...
     A sender MSH should not send the next message till it receives 
     an Acknowledgement Message from the Receiver.
    
  1>This will necessitate instantiating a separate MSH instance for each
recipient
     party, as it will not be fair for blocking outgoing messages to Parties
having
     a clear messaging channel while Messages to Parties with poor links are

     successfully sent (tried to send).   

  2>This will also mean that separate outbound message queues are to be 
     maintained for each recipient. For each recipient Party, I will have to
manage
     the lifecycle of a dedicated SequenceCounter i.e.recycling the
SequenceCounter
     upon tripping over the max as well as when they get stale after "long
time".
     In hub scenarios, this will amount to a lot of runtime objects creation
and
     will also require an ongoing activity in the server to manage the
queues and
     lifecycles of the SequenceCounter objects.

  3>With lots of outbound messages for the same recipient Party, there
     should be some provision for parallelism. Typically when servers can
handle multiples
     of parallel message exchanges, the RM spec will necessitate using a
single
     pipeline resulting into underutilization of capacity and slowing down
of the entire 
     process. Critical messages requiring immediate transfer might get stuck
in the
     queue for unreasonable amount of time.

Or am I missing something very fundamental. It's been a while I have done
ebXML,
and with the Tokyo POC not very far, I got to catch up :-).

thanks,
Sanjay Patil
----------------------------------------------------------------------------
------------------------------
Work Phone: 408 350 9619
http://www.netfish.com