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] discussion of issue i009


Correct me if I'm wrong, but this seems to presume that an RMD will
implement one and only one type of DA for every sequence that it
services. Skirting the issue of sequence granularity for now, it still
seems fairly likely that different AS-AD pairs may share an RMD but
require different delivery assurances to function correctly.

I think your suggestion is a useful way for the RMD to declare which DAs
it is capable of and configured to support, but the actual DA that is in
effect for a particular sequence should be included in the
CreateSequenceResponse message.

- g

p.s. For those wishing to see a use case that justifies the need for an
RMS to have knowledge of the DA in effect between the RMD and AD see
UC-5 "Smartphone Subscribes to Service" in

> -----Original Message-----
> From: Christopher B Ferris [mailto:chrisfer@us.ibm.com] 
> Sent: Wednesday, September 14, 2005 9:40 AM
> To: ws-rx@lists.oasis-open.org
> Subject: [ws-rx] discussion of issue i009
> All,
> This email is intended to start a discussion on issue i009 [1].
> The issue has to do with providing the RMD with the capacity 
> to advertise its DA QoS. It is somewhat related to issue 
> i024, raised by Ashok. However, I don't believe that the 
> resolutions need to be tied to one another.
> Basically, there is currently no specified means of declaring 
> the DA applied at a given RMD endpoint. It has been suggested 
> that the RMS (or AS) might have a vested interest in knowing, 
> a priori to establishing a Sequence with an RMD what DA would 
> be applied. For instance, it may require that the messages be 
> processed InOrder. If the RMD were not enforcing InOrder DA 
> at the RMD, then the source endpoint might choose not to 
> engage with that endpoint.
> I would propose that one way to resolve this would be to 
> define RM policy assertions that specify the DA.
> e.g. a psuedo-schema for this would be as follows:
> <wsrm:RMAssertion>
>   <wsrm:DeliveryAssertion mode="[AtLeastOnce|AtMostOnce|ExactlyOnce]" 
> ordered="[xs:boolean]"? ... >
>     ...
>   </wsrm:DeliveryAssertion>?
>   ...
> </wsrm:RMAssertion>
> Thus, an endpoint could declare its DA QoS in the policy 
> statement associated with the endpoint.
> Thoughts?
> [1]
> http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.ph
> p/14329/ReliableMessagingIssues.xml#i009
> Cheers,
> Christopher Ferris
> STSM, Emerging e-business Industry Architecture
> email: chrisfer@us.ibm.com
> blog: http://webpages.charter.net/chrisfer/blog.html
> phone: +1 508 377 9295
BEAWorld 2005: coming to a city near you.  Everything you need for SOA and enterprise infrastructure success.

Register now at http://www.bea.com/4beaworld

Santa Clara 27-29 Sep| London 11-12 Oct| Paris13-14 Oct| Prague18-19 Oct |Tokyo 25-26 Oct| Beijing 7-8 Dec

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