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.

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

request/response<br />

Parent elements<br />

Child<br />

elements<br />

Data type<br />

Number<br />

allowed<br />

SmartReply command<br />

request (section 2.2.2.18.1)<br />

SmartReply (section<br />

2.2.3.145)<br />

None string 1...1<br />

(required)<br />

The ClientId element value can be up to 40 characters in length and MUST be unique for each<br />

message, as the server will use the ClientId element value to identify duplicate messages. The<br />

ClientId element value can be a simple counter incremented for each new message.<br />

2.2.3.27.2 ClientId (Sync)<br />

The ClientId element is a required child element of the Add element in Sync command requests<br />

and responses that contains a unique identifier (typically an integer) that is generated by the client<br />

to temporarily identify a new object that is being created by using the Add element. The client<br />

includes the ClientId element in the Add element request that it sends to the server. The server<br />

response contains an Add element that contains the original client ID and a new server ID that was<br />

assigned for the object, which replaces the client ID as the permanent object identifier.<br />

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

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

request/response<br />

Parent<br />

elements<br />

Child<br />

elements<br />

Data type<br />

Number<br />

allowed<br />

Sync command request<br />

()section 2.2.2.19.1<br />

Add (section<br />

2.2.3.7.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 />

Add (section<br />

2.2.3.7.2)<br />

None string 1…1<br />

(required)<br />

The ClientId element is a unique identifier that consists of up to 64 digits and letters. The client<br />

generates this ID. The value only has to be unique for the device during the duration of the Sync<br />

request that adds the object to the server. The client stores the client IDs until the synchronization<br />

session is completed successfully, to make recovery easier if the synchronization process fails.<br />

An easy way to implement the client ID is to use a counter that is incremented for each new object<br />

that is created on the client.<br />

2.2.3.28 Collection<br />

The Collection element is used in the following command requests and responses:<br />

•GetItemEstimate command requests (section 2.2.2.7.1) and responses (section 2.2.2.7.2)<br />

•Sync command requests (section 2.2.2.19.1) and responses (section 2.2.2.19.2)<br />

The definition of the Collection element differs according to the context in which it is used. For<br />

more details, see section 2.2.3.28.1 and section 2.2.3.28.2.<br />

2.2.3.28.1 Collection (GetItemEstimate)<br />

The Collection element is a required child element of the Collections element in<br />

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

GetItemEstimate command responses. In both contexts, it contains elements that apply to a<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 />

118 / 369

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

Saved successfully!

Ooh no, something went wrong!