Share via

3.3.4.3.3.2 Content Upload

  • Article

The following sections specify best practices for uploading content modifications, read/unread state changes, deletions, and move operations that were performed while the client was offline. The following figure shows this process.

Best practices for Message Changes

Figure 6: Best practices for Message Changes

When uploading content differences, the client can send any combination of the following ROP requests:

  • RopSynchronizationImportMessageChange (section 2.2.3.2.4.2). Imports new messages or changes to existing messages.

  • RopSynchronizationImportMessageMove (section 2.2.3.2.4.4). Communicates the movement of messages between folders within the same mailbox.

  • RopSynchronizationImportDeletes (section 2.2.3.2.4.5). Imports deletions of messages.

  • RopSynchronizationImportReadStateChanges (section 2.2.3.2.4.6). Imports changes to the read state of messages.

These ROPs do not have to be sent in any specific order and can be mixed together. For example, all the deletions do not have to be uploaded before all the message moves, and all the message changes do not have to be uploaded before all the deletions.