RE: RE: Issue 146 proposed resolution

I buy that. However, while the base SOAP 1.2 processing model doesn't
address this directly I think it is important to enable this kind of
scenario as part of SOAP based systems. The term *sender* wasn't in this
case intended to be seen as a raw SOAP node but rather a part of an
application with a notion of the intended or ultimate destination of the
message.

Henrik Frystyk Nielsen
mailto:henrikn@microsoft.com

>>In this case, the party who the sender thinks is the ultimate 
>>destination....
>
>I don't disagree with the rest of your note, but this one line 
>does concern me.  To some people using the "actor" attribute 
>gives the sender some sort of routing or targetting mechanism. 
>We know that routing is definitely not what it is there for, 
>and targetting is only true so far as you can say "the node 
>that will process this block will act in 'this' role".  So, 
>when we talk about a sender "thinking" that a particular node 
>is the ultimate destination it sounds a little too close to 
>targetting a node by something like an IP address rather than 
>its role. A sender only has the notion of two things (w.r.t. 
>targetting or routing), and that is "next" (since he's the one 
>who opens up the socket) and "everything else" - which 
>technically could wind up being "next" depending on the roles 
>"next" chooses to take on.  I get a little concerned when I 
>see text that seems to imply the sender has any more control 
>or knowledge beyond this.  So, I don't believe the sender can 
>ever really "think" a certain party(node) is the ultimate 
>destination - he must always look at "next" as sort of a black 
>box - "next" could be the end of the road or could be just the 
>beginning - its a total unknown.

Received on Thursday, 15 November 2001 12:19:06 UTC