[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ws-rx] Use Case for having Reliability assurances at finer granularitythan Port Type
Tom Is that a correct reading of the specification? I thought that the restriction to portType is the WSRM Policy. Since the policy does not define the GD, DE, or OD, then this does not affect those. As I understand the submitted spec qos's are based on a private contract between the RM destination and the application destination, which could well be more finely grained than per porttype since it is not defined in the spec or policy at all. Paul Paul Fremantle, STSM, WebServices standards and architecture Hursley WebServices Team Consulting IT Specialist IBM Hursley Lab (MP 189) Winchester, SO21 2JN, UK ph+fax 44 (0) 1962 815 078 int ph: 245 078 pzf@uk.ibm.com "God, however, has chosen the most perfect world, that is to say the one which is at the same time the simplest in hypotheses and the richest in phenomena." Liebniz Tom Rutt <tom@coastin.com> on 27/06/2005 21:59:49 Please respond to tom@coastin.com To: wsrx <ws-rx@lists.oasis-open.org> cc: Subject: [ws-rx] Use Case for having Reliability assurances at finer granularity than Port Type The current WS-reliable messaging contribution does not support the application of reliability quality of service at a finer granularity than port type. I provide an example interface definition (which would map to a WSDL port type) Interface (Broker){ Operation Buy(in AccountNo, in StockName, in NumberOfShares): Operation Sell(in AccountNo, in StockName, in NumberOfShares); Operation UpdateInfo(in AccountNo, in CustomerAddress, in CustomerPhoneNo); Operation query (in AccountNo, out SequenceOf {StockName, NumberOfShares} } Buy and Sell need to be protected for guaranteed delivery, duplicate elim, and ordered delivery. UpdateInfo only needs to be protected for guaranteed delivery (it is idempotent). Query needs no reliability Qos. the query operation would not use ws-reliability at all. For this use case, the sender should be able to set up two Reliability message sequences, one with all qos enabled, the other with only Guaranteed delivery enabled. -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]