Re: [ws-rx] i090 - What is Offer good for anyway?

[Paul Fremantle <paul@wso2.com>]

Doug


 > Solving the anonymous replyTo with firewalls is not an RM specific 
problem and I'd much prefer
 > a solution that didn't require RM to be used.

The WS-A model (and even dumb old pre-WSA SOAP) already deals with the 
non-reliable firewall case that we are talking about here. But solving 
the *reliable* firewall case does seem to be a RM specific problem.
> w.r.t DougB's scenario...let's look at this differently, forget about RM
> for a minute and let's take the case where there are two clients talks
> to one server.  Both clients send a request message (w/o RM) to the 
> server
> at the same time, and they both include an anonymous wsa:ReplyTo. 
>  Hopefully,
> we can all agree that if the server decided to send client 1's 
> response to
> client 2 and client 2's response to client 1 that people would not be
> happy.  So, now let's add RM into the picture and simply make both 
> clients
> use the same RM sequence.
> Nothing different should happen w.r.t. which client
> _should_ get which response - in this case all RM is buying us is that 
> the
> messages will be reliably delivered and probably done so InOrder. 
I agree. And I would expect in this asynchronous model that the 
relatesTo headers would be used to correlate the messages.

But because in this scenario they both use the same sequence - and 
therefore the same offer, then according to the model I have proposed, 
the Offer-RMD must be able to deal with both these responses. It doesn't 
mean that the responses end up in the wrong place, simply that they 
share the same (Offered) RMD.
>  Yet, the approach you seem to be advocating is that mixing up the 
> responses
> would be ok. 
Where did you read that?
> Without some additional mechanisms (or at least good text) in
> place how can the server know which anonymous client should get which 
> response
> unless its uses the original http socket? 
No, the relatesTo is generally the way that you identify which client 
gets which response in an asynchronous case. Not the socket. I don't see 
why we need extra text for that because its just Plain Old WSA.
> Simply because they're both using
> the same inbound RM sequence doesn't mean that the RMD is free to mix up
> their responses. 
I agree.

Paul

-- 

Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://feeds.feedburner.com/bloglines/pzf
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com