Export (0) Print
Expand All

3.1.1 Abstract Data Model

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that specified in this document.

This protocol enables client applications either to request complete synchronization information from the server or to request incremental synchronization from the last synchronization information request. If the optional SyncState element of the SyncFolderHierarchyType complex type (section 3.1.4.1.3.6) is included in a SyncFolderHierarchy operation (section 3.1.4.1) request, or if the SyncState element of the SyncFolderItemsType complex type (section 3.1.4.2.3.8) is included in a SyncFolderItems operation (section 3.1.4.2), the server MUST return incremental synchronization information from the last synchronization request.

The contents of the SyncState elements are opaque to the client application; the client uses either the SyncState element of the SyncFolderHierarchyResponseMessageType complex type (section 3.1.4.1.3.4) that was returned by the previous SyncFolderHierarchy operation request, or the SyncState element of the SyncFolderItemsResponseMessageType complex type (section 3.1.4.2.3.6).

Client applications that use incremental synchronization for folder hierarchy synchronization MUST store the contents of the SyncState element of the SyncFolderHierarchyResponseMessageType complex type for subsequent requests.

Client applications that use incremental synchronization for item synchronization MUST store the contents of the SyncState element of the SyncFolderItemsResponseMessageType complex type for subsequent requests.

Show:
© 2014 Microsoft