OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ws-rx] Revised proposal #2 for i122 - i124

Marc Goodner wrote:
> Prateek, 
> I do not agree with this direction. Your proposal does not add anything
> that was not already in the previous proposal we made to the TC. All it
> does is move the STR from the body to the header. I don't understand
> this pursuit to purge RM of primitives from WSS (primitives intended for
> such reuse) when no exception is taken to the extensive reuse of
> primitives from WS-Addressing. 

I don't understand the comparison with WS-Addressing.

EPRs are references (dare I say identifiers [1] ;-) ) that 
specific/identify the place where messages are to be sent. RM is about 
reliably sending messages to endpoints and receiving acks at specific 
endpoint. EPRs are quite fundamental to message passing in WS-<splat>. I 
would argue more so than even SOAP. OTOH, security is typically 
architected as a separate entity (solved/implemented in once place but 
used in other places) that is composable. Other layers aren't quite 
aware of the details of it. In the same sense that reliable messaging 
isn't tightly coupled with transactions at the RM protocol level even 
though secure-reliable-transacted WS are quite important. They are 
separate but composable.

Good evidence for this is the fact that in WS-I the Basic Profile WG 
charter [2] was modified to include WS-Addressing (along with SOAP and 
WSDL) in the Basic Profile. Security profile is a separate profile in WS-I.


[1] http://www.w3.org/2002/ws/addr/wd-issues/Overview.html#i001
[2] http://www.ws-i.org/docs/charters/WSBasic_Profile_Charter2-1.pdf


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]