Server Has No Changed Items for the Client

Server Has No Changed Items for the Client

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. In this scenario, the client requests an updated manifest from the server by passing its previous collblob, and the server has no changed items to report to the client. In effect, the manifest returned by the server is empty, and the client already has an updated collblob. Under these circumstances, the server returns an empty repl XML Element as a child of the multistatus XML Element. If the client receives an empty repl XML Element from the server, the client should assume that the manifest is empty or that there are no new items that match the criteria.

Request

SEARCH /exchange/user0/inbox HTTP/1.1
Host: example.com
Content-type: text/xml
Content-length: {insert length here}

<?xml version="1.0"?>
<D:searchrequest xmlns:D="DAV:"
    xmlns:R="https://schemas.microsoft.com/repl/"
    xmlns:M="urn:schemas:mail:">
    <R:repl>
	<R:collblob>clientopaquedata</R:collblob>
    </R:repl>
    <D:sql>
	SELECT 'urn:schemas:mail:Size', 'urn:schemas:mail:Importance',
               'https://schemas.microsoft.com/repl/resourcetag'
		FROM SCOPE ('SHALLOW TRAVERSAL OF "/exchange/user0/inbox"')
    </D:sql>
</D:searchrequest> 

Response

HTTP/1.1 207 Multi-Status
Content-type: text/xml
Content-length: {insert length here}

<?xml version="1.0"?>
<D:multistatus xmlns:D="DAV:"
    xmlns:R="https://schemas.microsoft.com/repl/"
    xmlns:M="urn:schemas:mail:">
	<R:repl></R:repl>
</D:multistatus>

Send us your feedback about the Microsoft Exchange Server 2003 SDK.

This topic last updated: December 2004

Build: June 2007 (2007.618.1)

© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.