element <queryRequest> (global)
Namespace:
http://schemas.microsoft.com/hs/2001/10/core
Type:
queryRequestType
Content:
complex, 2 elements
Defined:
globally in hsdl.xsd; see XML source
Used:
never
XML Representation Summary
<queryRequest>
   
Content: 
</queryRequest>
Content model elements (2):
changeQuery (in queryRequest), xpQuery (in queryRequest)
Annotation
The purpose of the <b>queryRequest</b> message is to return, in the <b>queryResponse</b> message, information from the specified document. The message is designed to carry multiple query operations in a single request message. This allows applications to specify efficient queries and address different pieces of the document in a single message transmission. <p/> The <b>queryRequest</b> message may contain zero or more <b>xpQuery</b> elements. These elements specify data queries on the specified document. They contain an XPath expression that selects a set of nodes, and by using <b>minOccurs</b> and <b>maxOccurs</b>, they can control how many nodes are returned in a given operation. <p/> The <b>queryRequest</b> message may contain zero or more <b>changeQuery</b> elements. The purpose of this element is to aid client software in building caches populated with .NET My Services data. These elements are designed to issue a query relative to a <b>changeNumber</b>, and instead of returning simply content, they return a summary of changed or deleted <b>blue</b> items. <p/> The .NET My Services effort is likely to evolve to include support for XML Query. In anticipation of this, plans include support for zero or more <b>xmQuery</b> elements that will be used to encapsulate the XML Query language.
XML Source (see within schema source)
<xsd:element name="queryRequest" type="queryRequestType">
<xsd:annotation>
<xsd:documentation>
The purpose of the
<b>queryRequest</b>
message is
to return, in the
<b>queryResponse</b>
message, information
from the specified document. The message is designed to carry multiple
query operations in a single request message. This allows applications
to specify efficient queries and address different pieces of the document
in a single message transmission.
<p/>
The
<b>queryRequest</b>
message may contain zero or more
<b>xpQuery</b>
elements. These elements
specify data queries on the specified document. They contain an XPath expression
that selects a set of nodes, and by using
<b>minOccurs</b>
and
<b>maxOccurs</b>
, they can control
how many nodes are returned in a given operation.
<p/>
The
<b>queryRequest</b>
message may contain zero or more
<b>changeQuery</b>
elements. The purpose
of this element is to aid client software in building caches populated with
.NET My Services data. These elements
are designed to issue a query relative to a
<b>changeNumber</b>
, and instead of returning
simply content, they return a summary of changed or deleted
<b>blue</b>
items.
<p/>
The .NET My Services effort is likely to evolve to include support for XML Query. In anticipation
of this, plans include support for zero or more
<b>xmQuery</b>
elements that will be used to
encapsulate the XML Query language.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
Content Element Detail (all declarations; 2/2)
changeQuery
Type:
changeQueryType, complex content
Defined:
locally within queryRequestType complexType
This element is used to request a list of updates relative to a single 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.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="changeQuery" type="changeQueryType">
<xsd:annotation>
<xsd:documentation>
This element is used to request a list of updates relative to a single
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:documentation>
</xsd:annotation>
</xsd:element>
xpQuery
Type:
xpQueryType, complex content
Defined:
locally within queryRequestType complexType
This element specifies an XPath query against the data contained 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.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="xpQuery" type="xpQueryType">
<xsd:annotation>
<xsd:documentation>
This element specifies an XPath query against the data contained
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:documentation>
</xsd:annotation>
</xsd:element>