2.2.4.4 FastTransfer Streams in ROPs
The following table describes how possible root elements in the FastTransfer stream correspond to Bulk Data Transfer operations defined in section 2.2.3. Every download operation has to be configured prior to being able to produce a FastTransfer stream. Configuration starts by sending one of the ROPs in the following table and then performing the additional ROP specific configuration steps, as specified in sections 3.3.4.1 and 3.3.4.3.2.
|
ROP that initiates an operation |
Root element in the produced FastTransfer stream |
ROP request buffer field conditions |
|---|---|---|
|
RopSynchronizationConfigure |
contentsSync |
The SynchronizationType field is set to Contents (0x01). |
|
hierarchySync |
The SynchronizationType field is set to Hierarchy (0x02). |
|
|
RopSynchronizationGetTransferState |
state |
Always. |
|
RopFastTranserSourceCopyTo RopFastTranserSourceCopyProperties |
folderContent |
The InputServerObject field is a Folder object.<25> |
|
messageContent |
The InputServerObject field is a Message object. |
|
|
attachmentContent |
The InputServerObject field is an Attachment object.<26> |
|
|
RopFastTranserSourceCopyMessages |
messageList |
Always. |
|
RopFastTranserSourceCopyFolder |
topFolder |
Always. |
FastTransfer streams produced by operations initiated by the RopSynchronizationConfigure ROP are intended for processing on the client only.
FastTransfer streams produced by operations initiated with the RopFastTransferSource* ROPs can either be processed by the client or uploaded to the server through an operation initiated by the RopFastTransferDestinationConfigure ROP. For details about the applicability of FastTransfer streams to FastTransfer upload operations, see section 2.2.3.1.2.1.1.