Re: [ws-rx] PR001 - Feedback on MSFT's MC proposal

[Doug Davis <dug@us.ibm.com>]

Yup - as long as you're willing to live
with all of the restrictions I listed in my previous note.  The RM
spec should allow for lots of different impl choices - not just one.
-Doug

"Paul Fremantle" <paul@wso2.com>
Sent by: paulfremantle@gmail.com

11/05/2006 05:19 AM

To	Doug Davis/Raleigh/IBM@IBMUS
cc	"Durand, Jacques R." <JDurand@us.fujitsu.com>, "Marc Goodner" <mgoodner@microsoft.com>, ws-rx@lists.oasis-open.org
Subject	Re: [ws-rx] PR001 - Feedback on MSFT's MC proposal

 Looking at another use-case -
say there's an RMS is implemented as a gateway/proxy  - where all
messages leaving the environment heading for another destination are placed
into the same RM Sequence - because there's (as I've heard Chris describe
it) "one big pipe" between the two companies.  In this scenario
the gateway has no idea of the MEPs being used or the application semantics
involved - all it basically does is add the RM Sequence header to the messages.
 It then becomes up to each individual client (since its the only
one that knows the MEPs and application semantics) to request the responses
that may be expected.  Again, we need to be able to identify which
response goes to which client/MakeConnection request.


Doug

This is a usecase we are currently working on implementing using Apache
Synapse. In our model, the clients do not need to know anything about MakeConnection.
The gateway correlates responses back to clients using either WSA semantics
(replyTo and messageID), or by holding onto the socket and correlating
between the incoming client's socket and the WSA messageID that we assign
to outgoing messages. The gateway polls for responses on the MC(sequenceID)
(in the current model). I see no reason why the model Marc is proposing
wouldn't also work. 

So while I agree completely you can implement the model the way you are
suggesting, it isn't at all a necessity. In fact the model we are implementing
supports anonymous clients who do not even implement WSA, let alone WSRM.
For example, JMS clients can be bridged into WSRM reliably. 

Paul