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] [i061] YAP (yet another proposal)



Marc,

We need to define the semantic of the use of anon URI to close the gap with WS-A's definition of
anonymous. I have taken your feedback into consideration and would like to offer up this:

After some internal discussions we'd like to offer up this proposal for i061.  A lot of rethinking has happened based on the long discussions in the WSA TC regarding what anon EPRs mean and which spec should say what.  WSA seems to be headed down the path of saying what anon EPRs mean for their EPRs (e.g. replyTo, faultTo...) and leaving it to other specs to define what anon means for the EPRs those specs define (like leaving AcksTo for the RM spec to define).  So, in keeping with that thinking, here's the new proposed changes:

In the Requested Ack section, change:

The RM Source may request an acknowledgement message from the RM Destination at any time by including an <wsrm:AckRequested> header block in the message.

to

The RM Source may request an acknowledgement message from the RM Destination at any time by including an <wsrm:AckRequested>  header block in any message targeted to the RM Destination.


In the Seq Ack section, change:

The <wsrm:SequenceAcknowledgement> header block MAY be transmitted independently or included on return messages.

to

The <wsrm:SequenceAcknowledgement> header block MAY be transmitted independently or included on any message targeted to the AcksTo EPR.


And in the Seq Ack section, after the first para add:


A RMD MAY include a wsrm:SequenceAcknowledgement header block on any SOAP envelope targetted to the
endpoint referenced by the wsrm:AcksTo EPR.
 
A wsrm:AcksTo EPR MAY specify the WS-Addressing anonymous URI as its address. When the wsrm:AcksTo EPR specifies
the WS-Addressing anonymous URI as its address, the RMD MUST transmit any wsrm:SequenceAcknowledgement headers  

for the created Sequence in a SOAP envelope to be transmitted on the protocol binding-specific channel
provided by the context of a received message containing a SOAP envelope that contains a wsrm:Sequence  

header block and/or a wsrm:AckRequested header block for that same Sequence identifier.


Note that this practice MAY require that the RMD endpoint return a SOAP envelope specifically for the purpose of  
transmitting the wsrm:SequenceAcknowledgement in certain cases where there would not normally be  

a SOAP envelope carried in the response message, such as a WSDL oneway operation or in the case
where a wsrm:AckRequested header block is sent independently of any application-level message content.


Cheers,

Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
phone: +1 508 377 9295


"Marc Goodner" <mgoodner@microsoft.com> wrote on 02/23/2006 12:58:12 PM:

> I think we’re getting closer Doug. Most of this looks correct to me.
> A few comments.

>  
> First, I don’t think quotes should ever be used around words in
> normative text. To me that is a signal that better words need to be found.

>  
> Why describe “piggy-backing”? It isn’t adding anything to the
> proposal, I suggest cutting that sentence.

>  
> I’m not convinced that the paragraph describing returning a SOAP
> envelope for a one-way message to return the acks is needed. I also
> dislike the use of “manufacture”. I think all you need to say is
> that a SOAP message would be returned to the AcksTo EPR with an
> empty body. I think you over clarified there. Furthermore why do you
> think this only applies to anon-uri? Why would this practice be
> disallowed for an addressable AcksTo EPR? I think this description
> and the anon-uri description are orthogonal.

>  
> Marc Goodner
> Technical Diplomat
> Microsoft Corporation
> Tel: (425) 703-1903
> Blog: http://spaces.msn.com/mrgoodner/
>
> From: Doug Davis [mailto:dug@us.ibm.com]
> Sent: Wednesday, February 22, 2006 7:17 AM
> To: ws-rx@lists.oasis-open.org
> Subject: [ws-rx] [i061] YAP (yet another proposal)

>  
>
> After some internal discussions we'd like to offer up this proposal
> for i061.  A lot of rethinking has happened based on the long
> discussions in the WSA TC regarding what anon EPRs mean and which
> spec should say what.  WSA seems to be headed down the path of
> saying what anon EPRs mean for their EPRs (e.g. replyTo, faultTo...)
> and leaving it to other specs to define what anon means for the EPRs
> those specs define (like leaving AcksTo for the RM spec to define).
> So, in keeping with that thinking, here's the new proposed changes:
>
> In the Requested Ack section, change:
> The RM Source may request an acknowledgement message from the RM
> Destination at any time by including an <wsrm:AckRequested> header
> block in the message.
> to
> The RM Source may request an acknowledgement message from the RM
> Destination at any time by including an <wsrm:AckRequested>  header block in
> any message targeted to the RM Destination.
>
> In the Seq Ack section, change:
> The <wsrm:SequenceAcknowledgement> header block MAY be transmitted
> independently or included on return messages.
> to
> The <wsrm:SequenceAcknowledgement> header block MAY be transmitted
> independently or included on any message targeted to the AcksTo EPR.
>
> And in the Seq Ack section, after the first para add:
>
> A RMD MAY include a wsrm:SequenceAcknowledgement header block on any
> SOAP envelope targetted to the
> endpoint referenced by the wsrm:AcksTo EPR. This concept is often
> referred to as "piggy-backing"  
> Sequence acknowledgements.
>  
> A wsrm:AcksTo EPR MAY specify the WS-Addressing anonymous URI as its
> address. When the wsrm:AcksTo EPR specifies
> the WS-Addressing anonymous URI as its address, the RMD MUST
> transmit any wsrm:SequenceAcknowledgement headers  
> for the created Sequence in a SOAP envelope to be transmitted on the
> protocol binding-specific channel
> provided by the context of a received message containing a SOAP
> envelope that contains a wsrm:Sequence  
> header block and/or a wsrm:AckRequested header block for that same
> Sequence identifier. Note that this  
> practice MAY require that the RMD "manufacture" a SOAP envelope
> specifically for the purpose of  
> transmitting the wsrm:SequenceAcknowledgement in certain cases where
> there would not normally be  
> a SOAP envelope carried in the response message such as a WSDL
> oneway operation or in the case
> where a wsrm:AckRequested header block is sent independently of any
> application-level message content.
>
>
> thanks
> -Doug


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