[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW ISSUE: Acknowledgement Interval in CreateSequenceResponse
Title - Acknowledgement Interval in CreateSequenceResponse Description - Propose moving AI from Policy to the CreateSequenceResponse Justification - AcknowledgementInterval is not constraint or feature of an endpoint, it is a protocol parameter of a given sequence. Moving it out of policy has a number of benefits. It reduces the reliance on Policy and WSDL for simple devices, allowing them to ascertain this value without supporting either of those standards. It makes it clear what the ack interval is for any sequence. Further it seems unrealistic that a service would be chosen on the basis of AckInterval. Target - core / design Type: design Proposal: Modifications to the WSRM spec - Based on WD8 After line 302 insert: <wsrm:AcknowledgementInterval Milliseconds="xs:unsignedLong" ... /> ? After line 326 Insert: /wsrm:CreateSequenceResponse/wsrm:AcknowledgementInterval This element, if present, specifies the duration after which the RM Destination will transmit an acknowledgement. If omitted, there is no implied value. /wsrm:CreateSequenceResponse/wsrm:AcknowledgementInterval/@Milliseconds The acknowledgement interval, specified in milliseconds. Changes to Policy document based on WD3. Remove lines 101-108 Remove line 113 Remove lines 125-129 Remove line 164 (AI example) At line 179 Remove text: "Line (13) indicates the RM Destination may buffer acknowledgements for up to two-tenths of a second." Paul -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle paul@wso2.com "Oxygenating the Web Service Platform", www.wso2.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]