[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrm] Discussion on Issues Rel 108 and 115
Unification of Callback and Poll Response. The Current schema for ResponseType is as follows: <!-- Response Header Type and it's elements --> <xsd:complexType name="ResponseType"> <xsd:complexContent> <xsd:extension base="wsrm:RmBaseType"> <xsd:sequence> <xsd:element name="RefToMessageIds" type="wsrm:RefToMessageIdsType" maxOccurs="unbounded"/> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:complexType name="RefToMessageIdsType"> <xsd:complexContent> <xsd:extension base="wsrm:EmptyType"> <xsd:sequence> <xsd:element name="SequenceNumberRange" type="wsrm:SequenceNumberRangeType" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> <xsd:attribute name="groupId" type="wsrm:MIDType"/> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:complexType name="SequenceNumberRangeType"> <xsd:complexContent> <xsd:extension base="wsrm:EmptyType"> <xsd:attribute name="from" type="xsd:unsignedLong"/> <xsd:attribute name="to" type="xsd:unsignedLong"/> </xsd:extension> </xsd:complexContent> </xsd:complexType> ------ When used for an ack with the Response Reply pattern, the receiving RMP is restricted to ack only the message in the Request. However, it must populate both the From And To field of the sequence no range, just to send a single sequence number in the group. A fault is sent using the Fault element with response reply pattern, in the http response. Was it our intent to be so verbose for the single message ack in the REsponse reply pattern case? If not, why should be have the same schema for the single ack as for the multiple ack? -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@fsw.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]