W3C home > Mailing lists > Public > public-ws-async-tf@w3.org > June 2005

RE: Another proposal for async extensions

From: Yalcinalp, Umit <umit.yalcinalp@sap.com>
Date: Thu, 16 Jun 2005 21:22:07 +0200
Message-ID: <2BA6015847F82645A9BB31C7F9D6416515DB48@uspale20.pal.sap.corp>
To: "Marc Hadley" <Marc.Hadley@Sun.COM>
Cc: <public-ws-async-tf@w3.org>

 

> -----Original Message-----
> From: Marc Hadley [mailto:Marc.Hadley@Sun.COM] 
> Sent: Thursday, Jun 16, 2005 12:17 PM
> To: Yalcinalp, Umit
> Cc: public-ws-async-tf@w3.org
> Subject: Re: Another proposal for async extensions
> 
> On Jun 16, 2005, at 3:06 PM, Yalcinalp, Umit wrote:
> >>
> >> 2.1 Extend the existing wsaw:UsingAddressing Element
> >>
> >> Add an attribute 'asyncOnly' with a default value of 'false'. When
> >> 'true' the endpoint only supports async interactions.
> >>
> >>
> >
> > How about supporting async, noAsync, or both?
> >
> > We would like an endpoint to support all three cases. Would you  
> > consider
> > that? This is in essence the guts of our original proposal...
> >
> You mean something like:
> 
> <wsaw:UsingAddressing responseChannel="anonymous|specified|both">
>    <wsaw:ResponseBinding>...</wsaw:responseBinding>
> </wsaw:UsingAddressing>
> 
> where responseChannel="anonymous" means [reply endpoint] and [fault  
> endpoint] can only be anonymous, responseChannel="specified" means  
> [reply endpoint] and [fault endpoint] can not be anonymous, and  
> responseChannel="both" means [reply endpoint] and [fault endpoint]  
> can either be anonymous or something else (as further constrained by  
> the child wsaw:ResponseBinding elements).
> 

Yes. This was pretty much what we were going to propose collectively
which I have not got around writing... 

> Works for me.
> 
> Marc.
> 
> >
> >
> >> Add a wsaw:ResponseBinding child element with cardinality
> >> [0..unbounded]. The value of each of these is a binding
> >> identification URI that specifies that the given endpoint can
> >> support
> >> [reply endpoint] and [fault endpoint] destinations using the
> >> appropriate binding. If wsaw:UsingAddressing/@asyncOnly='true' then
> >> there must be at least one 
> wsaw:UsingAddressing/wsaw:ResponseBinding
> >> element.
> >>
> >> If there are zero 
> wsaw:UsingAddressing/wsaw:ResponseBinding elements
> >> then the only [destination] supported for [reply endpoint]
> >> and [fault
> >> endpoint] is the anonymous URI.
> >>
> >> [1] http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#soapinhttp
> >> [2] http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-
> >> soap.html?content-type=text/html;%20charset=utf-8#s12feature
> >> [3] http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-
> >> soap.html?content-type=text/html;%20charset=utf-8#s12module
> >> [4] http://www.w3.org/TR/2003/REC-soap12-part2-20030624/
> >> #tabreqstatereqtrans
> >> [5] http://www.w3.org/TR/2003/REC-soap12-part2-20030624/
> >> #tabresstaterecheads
> >>
> >> ---
> >> Marc Hadley <marc.hadley at sun.com>
> >> Business Alliances, CTO Office, Sun Microsystems.
> >>
> >>
> >>
> >>
> >
> >
> 
> ---
> Marc Hadley <marc.hadley at sun.com>
> Business Alliances, CTO Office, Sun Microsystems.
> 
> 
> 
Received on Thursday, 16 June 2005 19:22:42 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 16 June 2005 19:22:43 GMT