11.01.2015 Views

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

2.2.3.156.2 SyncKey (FolderSync)<br />

The SyncKey element is a required child element of the FolderSync element in FolderSync<br />

command requests and an optional child element of the FolderSync element in FolderSync<br />

command responses. In both contexts, it is used by the server to track the current state of the<br />

client.<br />

All elements referenced in this section are defined in the FolderHierarchy namespace.<br />

<strong>Command</strong><br />

request/response<br />

Parent elements<br />

Child<br />

elements<br />

Data type<br />

Number<br />

allowed<br />

FolderSync command<br />

request (section 2.2.2.4.1)<br />

FolderSync<br />

(section 2.2.3.67)<br />

None<br />

string ([<strong>MS</strong>-<br />

ASDTYPE] section<br />

2.6)<br />

1…1<br />

(required)<br />

FolderSync command<br />

response (section 2.2.2.4.2)<br />

FolderSync None string 0…1<br />

(optional)<br />

After successful folder synchronization, the server MUST send a synchronization key to the client.<br />

The client MUST store this key and send the key back to the server the next time the folder<br />

hierarchy is synchronized or updated. The server MUST check the value of the key to make sure the<br />

value of the SyncKey element provided in the request matches a synchronization key value on the<br />

server. The server MUST return a Status element (section 2.2.3.152.4) value of 9 if the value of the<br />

SyncKey element does not match the value of the synchronization key on the server.<br />

The client MUST store the synchronization key as an opaque string of up to 64 characters.<br />

If a synchronization error occurs, and the FolderSync response contains a Status element value of<br />

9 (see section 2.2.3.152.4) then the client MUST restart the synchronization process with a<br />

synchronization key of 0. The client's folder hierarchy list MUST be rebuilt and any changes that<br />

existed on the client that had not been propagated to the server prior to the error SHOULD be sent<br />

after the FolderSync operation is complete.<br />

2.2.3.156.3 SyncKey (GetItemEstimate)<br />

The airsync:SyncKey element is a required child element of the Collection element in<br />

GetItemEstimate command requests that represents the current state of a collection.<br />

Elements referenced in this section are defined in the GetItemEstimate namespace, except where<br />

otherwise indicated by the presence of a namespace prefix (as defined in section 2.2.1).<br />

<strong>Command</strong> request/response<br />

Parent elements<br />

Child<br />

elements<br />

Data type<br />

Number<br />

allowed<br />

GetItemEstimate command<br />

request (section 2.2.2.7.1)<br />

Collection<br />

(section<br />

2.2.3.28.1)<br />

None<br />

string ([<strong>MS</strong>-<br />

ASDTYPE] section<br />

2.6)<br />

1…1<br />

(required)<br />

The value of the element is examined by the server to determine the state of the synchronization<br />

process. The airsync:SyncKey element is the first child element of the Collection element (section<br />

2.2.3.28.1) in a GetItemEstimate command request.<br />

The airsync:SyncKey element value used within the GetItemEstimate requests is the same as<br />

the one returned within the Sync responses. The server does not update the airsync:SyncKey<br />

value on GetItemEstimate requests. For more details about the airsync:SyncKey element, see<br />

[<strong>MS</strong>-<strong>ASCMD</strong>] — v20110315<br />

<strong>ActiveSync</strong> <strong>Command</strong> <strong>Reference</strong> <strong>Protocol</strong> <strong>Specification</strong><br />

Copyright © 2011 Microsoft Corporation.<br />

Release: Tuesday, March 15, 2011<br />

245 / 369

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!