[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

The inline method of delivering binary content is including data encoded with base64 encoding inside
the WBXML. The inline approach generally requires the client to read the whole response into
memory in order to parse it, thereby consuming a large amount of memory.
Multipart
The multipart method of delivering content is a multipart structure with the WBXML being the first
part, and the requested data populating the subsequent parts. This format enables a client to handle
large files without consuming large amounts of memory, because a file is read in pieces, one piece
at a time.
The multipart approach enables the client to parse the small WBXML part, obtain references to the
binary parts, and handle the binary parts as necessary, without reading the entire response into
memory.
Multipart Request
If the client wants to have the document or documents returned in multipart format, the only
difference between this request and the inline content request is the addition of the following HTTP
header:
MS-ASAcceptMultiPart: T
If this header is not present, then the server uses the default value of "F" (FALSE), and returns
content inline. If the header is set to "T" (TRUE), then the server returns the document contents by
using the multipart format.
The following is a sample request for the test.txt document in a UNC share:
POST /Microsoft-Server-
ActiveSyncCmd=ItemOperations&User=administrator&DeviceId=v140Device&DeviceType=PocketPC
Content-Type: application/vnd.ms-sync
MS-ASProtocolVersion: 14.1
MS-ASAcceptMultiPart: T
DocumentLibrary
\\feod31\public\test.txt
The following is a sample response to the request for the test.txt document.
HTTP/1.1 200 OK
Content-Type: application/vnd.ms-sync.multipart
1
1
\\contoso\test.txt
0-999
91646690
[MS-ASCMD] — v20110315
ActiveSync Command Reference Protocol Specification
Copyright © 2011 Microsoft Corporation.
Release: Tuesday, March 15, 2011
38 / 369