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.

20<br />

<br />

Income generated by the sales department<br />

in April can be attributed to the following...<br />

<br />

<br />

IPM.Note<br />

28591<br />

<br />

urn:content-classes:message<br />

<br />

1<br />

…<br />

…<br />

<br />

<br />

<br />

<br />

4.10.4 Fetching an Attachment<br />

The following sections show how the client retrieves a new message with an attachment. The client<br />

uses the Sync command (section 2.2.2.19) to synchronize a new message with an attachment to<br />

the client and then uses the ItemOperations command (section 2.2.2.8) to retrieve the<br />

attachment.<br />

In the XML schema code, HTML strings are escaped by using "&lt;" and "&gt;". However, as these<br />

values are passed over the wire, they are passed in their original HTML format, as "".<br />

4.10.4.1 Sync Request<br />

The following example shows the Sync command request (section 2.2.2.19.1) sent from the client<br />

to the server to synchronize a new message with an attachment to the client.<br />

<br />

<br />

<br />

<br />

1<br />

7<br />

<br />

<br />

<br />

<br />

<br />

4.10.4.2 Sync Response<br />

The following example shows the Sync command response (section 2.2.2.19.2) sent from the<br />

server to the client.<br />

<br />

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

303 / 369

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

Saved successfully!

Ooh no, something went wrong!