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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

section 2.2.3.156.4. The server checks the value of the key to verify that the value of the<br />

airsync:SyncKey element provided in the request matches a airsync:SyncKey value on the<br />

server. The server MUST provide a Status element (section 2.2.3.152.6) value of 4 if the<br />

airsync:SyncKey value provided in the GetItemEstimate request does not match those expected<br />

within the next Sync command request (section 2.2.2.19.1).<br />

The airsync:SyncKey element value is a string value up to 64 characters in length.<br />

2.2.3.156.4 SyncKey (Sync)<br />

The SyncKey element is a required child element of the Collection element in Sync command<br />

requests and responses that contains a value that is used by the server to mark the synchronization<br />

state of a collection.<br />

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

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

request/response<br />

Parent elements<br />

Child<br />

elements<br />

Data type<br />

Number<br />

allowed<br />

Sync command request<br />

(section 2.2.2.19.1)<br />

Collection<br />

(section<br />

2.2.3.28.2)<br />

None<br />

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

ASDTYPE] section<br />

2.6)<br />

1…1<br />

(required)<br />

Sync command response<br />

(section 2.2.2.19.2)<br />

Collection<br />

(section<br />

2.2.3.28.2)<br />

None string 1…1<br />

(required)<br />

A synchronization key of value 0 (zero) initializes the synchronization state on the server and causes<br />

a full synchronization of the collection. The server sends a response that includes a new<br />

synchronization key value. The client MUST store this synchronization key value until the client<br />

requires the key value for the next synchronization request for that collection. When the client uses<br />

this synchronization key value to do the next synchronization of the collection, the client sends this<br />

synchronization key value to the server in a Sync request. If the synchronization is successful, the<br />

server responds by sending all objects in the collection. The response includes a new<br />

synchronization key value that the client MUST use on the next synchronization of the collection.<br />

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

The client MUST send a synchronization key value of 0 in an initial Sync request and the server<br />

sends a new synchronization key value in its response to the client. The client MUST NOT ignore the<br />

synchronization key value that is included in the initial response from the server.<br />

2.2.3.157 To<br />

The To element is a required child element of the ResolveRecipients element in<br />

ResolveRecipients command requests that specifies one or more recipients to be resolved. The To<br />

element is a required child element of the Response element in ResolveRecipients command<br />

responses that specifies a recipient to be resolved. The To element is an ANR search field. Its value<br />

can be up to 256 characters in length.<br />

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

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

request/response<br />

Parent elements<br />

Child<br />

elements<br />

Data type<br />

Number<br />

allowed<br />

ResolveRecipients ResolveRecipients None string ([<strong>MS</strong>- 1...1000<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 />

246 / 369

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

Saved successfully!

Ooh no, something went wrong!