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.

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

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

more details, see section 2.2.3.87.1 and section 2.2.3.87.2.<br />

2.2.3.87.1 MaxItems (GetItemEstimate)<br />

The airsync:MaxItems element is an optional child element of the airsync:Options element<br />

in GetItemEstimate command requests that specifies the maximum number of items to include in<br />

the response. This element can only be included in a request when the CollectionId element<br />

(section 2.2.3.29.1) is set to "RI" to specify a recipient information store; otherwise, the server will<br />

respond with a status 2 error. The value of the airsync:MaxItems element does not specify the<br />

limit of estimates available; rather, it only specifies the number of items, as a complete replacement<br />

would be double the number of items in the store (n deletes plus n additions).<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><br />

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

airsync:Options<br />

(section 2.2.3.107.1)<br />

None<br />

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

ASDTYPE]<br />

section 2.5)<br />

0...1<br />

(optional)<br />

Including airsync:MaxItems when the CollectionId element is set to anything other than "RI"<br />

results in an invalid XML error, Status element (section 2.2.3.152.6) value of 2.<br />

The result of including more than one airsync:MaxItems element as the child of the<br />

airsync:Options element is undefined. The server MAY return a protocol status error in response to<br />

such a command request.<br />

2.2.3.87.2 MaxItems (Sync)<br />

The MaxItems element is an optional child element of the Options element in Sync<br />

command requests that specifies the maximum number of recipients (that is, the top N most<br />

frequently used recipients) to keep synchronized from within the recipient information cache. This<br />

element MUST only be included in a request when the value of the CollectionId element (section<br />

2.2.3.29.5) maps to the recipient information cache. The value of the MaxItems element does not<br />

specify the maximum estimate of additions and deletions to make to the recipient information<br />

cache, it only specifies the number of recipients to keep synchronized. A complete replacement of<br />

each recipient would be double the number of MaxItems or items in the store, as each recipient<br />

update requires a deletion and an addition.<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 />

Options (section<br />

2.2.3.107.5)<br />

None<br />

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

ASDTYPE] section<br />

2.5)<br />

0...1<br />

(optional)<br />

163 / 369<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

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

Saved successfully!

Ooh no, something went wrong!