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.

Either the HeartbeatInterval element or the Wait element (section 2.2.3.171) can be included in<br />

a Sync command request, but not both. If both elements are included, the server response will<br />

contain a Status element value of 4.<br />

When the HeartbeatInterval element is used in a Sync command request, the element indicates<br />

to the server that a response SHOULD be delayed either until the interval, which is indicated by the<br />

contents of the HeartbeatInterval element, elapses or until any of the collections that are included<br />

in the request have changed.<br />

It is at the discretion of the client to send the HeartbeatInterval element; the server is only<br />

guaranteed to respond immediately when neither the HeartbeatInterval element nor the Wait<br />

element (section 2.2.3.171) are present. The client typically requires a server response immediately<br />

in the following cases:<br />

•The client adds new items by using the Add element (section 2.2.3.7.2). In this case, an<br />

immediate response is required because the client requires the server-provided item ID to track<br />

changes to those new items.<br />

•The client sends the server a Change element (section 2.2.3.23) that contains an important<br />

update. In this case, a delayed response increases the possibility that the client has to resend the<br />

change because of a lost connection.<br />

Although the server is only guaranteed to respond immediately when the HeartbeatInterval<br />

element and the Wait element (section 2.2.3.171) are not present, the server SHOULD always<br />

respond immediately to a Sync command request that includes an Add element or a Change<br />

element, unless the addition or change involves only flags.<br />

A flagging change or a move out of (and not into) a folder which is being synced SHOULD NOT<br />

cause the request to finish early.<br />

2.2.3.76 Id<br />

The Id element is a required child element of the Folder element in Ping command requests that<br />

specifies the server ID of the folder to be monitored.<br />

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

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

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

request/response<br />

Parent<br />

elements<br />

Child<br />

elements<br />

Data type<br />

Number<br />

allowed<br />

Ping command request<br />

(section 2.2.2.11.1)<br />

Folder (section<br />

2.2.3.62)<br />

None<br />

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

ASDTYPE] section<br />

2.6)<br />

1…1<br />

(required)<br />

The server ID of the folder is obtained from the folderhierarchy:ServerId element (section<br />

2.2.3.141) of a previous FolderSync command response (section 2.2.2.4.2) or FolderCreate<br />

command response (section 2.2.2.2). The Id element value can be up to 64 characters in length.<br />

2.2.3.77 IMEI<br />

The IMEI element is an optional child element of the Set element in Settings command requests<br />

that specifies a 15-character code that MUST uniquely identify a device.<br />

All elements referenced in this section are defined in the Settings namespace.<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 />

156 / 369

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

Saved successfully!

Ooh no, something went wrong!