Namespace: |
|
Content: |
complex, 2 elements |
Defined: |
globally in hsdl.xsd; see XML source |
Includes: |
definitions of 2 elements |
Used: |
at 1 location |
XML Representation Summary |
|||||
<...> |
|||||
|
|||||
</...> |
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="xpQuery" type="xpQueryType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element specifies an XPath query against the data contained
</xsd:documentation>
within the specified document. The element is contains an XPath expression that selects the nodes the client needs to extract from .NET My Services, and constraints on how many nodes the selection must match.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element is used to request a list of updates relative to a single
</xsd:documentation>
selected node and a <b>changeNumber</b>
value on that node. It is designed specifically
to support client-side caching of .NET My Services content. Any <b>xdb:blue</b>
node
can be selected with the <b>select</b>
attribute. It is an error condition to select more than a single node. While
this element does not support <b>minOccurs/maxOccurs</b>
attributes, it is as if
<b>minOccurs</b>
=0 and
<b>maxOccurs</b>
=1.
The response to this message is an <b>updateRequest</b>
message that contains the insert, replace,
and delete operations that should be processed by the client software to bring its cache up to date with respect to the change number specified in this element. <p/>
There will be times when the .NET My Services system will be unable to return a
<b>changeQueryResponse</b>
that is complete enough bring a client cache in sync. This
can occur when the client is way out of date and numerous delete operations have occurred. In these situations, a <b>changeQuery</b>
will simply fail with a fault condition
and, in response to this message, the client should discard and rebuild its cache. </xsd:complexType>
|
Type: |
changeQueryType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element is used to request a list of updates relative to a single
</xsd:documentation>
selected node and a <b>changeNumber</b>
value on that node. It is designed specifically
to support client-side caching of .NET My Services content. Any <b>xdb:blue</b>
node
can be selected with the <b>select</b>
attribute. It is an error condition to select more than a single node. While
this element does not support <b>minOccurs/maxOccurs</b>
attributes, it is as if
<b>minOccurs</b>
=0 and
<b>maxOccurs</b>
=1.
The response to this message is an <b>updateRequest</b>
message that contains the insert, replace,
and delete operations that should be processed by the client software to bring its cache up to date with respect to the change number specified in this element. <p/>
There will be times when the .NET My Services system will be unable to return a
<b>changeQueryResponse</b>
that is complete enough bring a client cache in sync. This
can occur when the client is way out of date and numerous delete operations have occurred. In these situations, a <b>changeQuery</b>
will simply fail with a fault condition
and, in response to this message, the client should discard and rebuild its cache. </xsd:element>
|
Type: |
xpQueryType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element specifies an XPath query against the data contained
</xsd:documentation>
within the specified document. The element is contains an XPath expression that selects the nodes the client needs to extract from .NET My Services, and constraints on how many nodes the selection must match. </xsd:element>
|