complexType "echoBackType"
Namespace:
http://schemas.microsoft.com/hs/2001/10/core
Content:
complex, elem. wildcard
Defined:
globally in hsinfra.xsd; see XML source
Includes:
definition of elem. wildcard
Used:
at 1 location
XML Representation Summary
<...>
   
Content: 
</...>
All Direct / Indirect Based Elements (1):
echoBack
Known Usage Locations
Annotation
The <b>echoBack</b> header is a header element that applications can use to pass additional correlation data or out-of-band data between the request and the response recipients. It is considered bad form to use this header during synchronous, piggy-backed responses (because in that situation, the call stack should be all that is required to keep sufficient context), or during cases where responses are not generated or are only generated during fault conditions. If the UUIDs in the <b>path</b>/<b>id</b> and <b>path</b>/<b>relatesTo</b> are insufficient to provide correlation data, the <b>echoBack</b> header can be used to pass arbitrarily structured XML between the service requester and the recipient of the associated .NET My Services response. <p/> .NET services make no attempt to process or inspect the contents of this header. They simply transmit the header from the request message to the response message and treat it as an opaque body of XML.
XML Source (see within schema source)
<xsd:complexType name="echoBackType">
<xsd:annotation>
<xsd:documentation>
The
<b>echoBack</b>
header is a header element that applications can use to pass additional correlation
data or out-of-band data between the request and the response recipients. It is considered bad form
to use this header during synchronous, piggy-backed responses (because in that situation, the call
stack should be all that is required to keep sufficient context), or during cases where responses
are not generated or are only generated during fault conditions. If the UUIDs in the
<b>path</b>
/
<b>id</b>
and
<b>path</b>
/
<b>relatesTo</b>
are insufficient to provide correlation data, the
<b>echoBack</b>
header can be
used to pass arbitrarily structured XML between the service requester and the recipient of the
associated .NET My Services response.
<p/>
.NET services make no attempt to process or inspect the contents of this header. They simply
transmit the header from the request message to the response message and treat it as an opaque body
of XML.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 1/1)
{any element with non-schema namespace}
Defined:
within (this) echoBackType complexType
XML Source (see within schema source)
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>