Other Local Events None. Client Details This section provides client-specific details related to bulk data transfer. The Mailbox Synchronization Protocol Specification [MS-OXCSYNC] also contains important details related to bulk data transfer. Abstract Data Object and Change Identification The following three alternative mechanisms are available to clients that need to create objects in their local replica without having immediate contact with the server to upload the differences. This is also known as working offline. Client-Assigned Internal Identifiers When this most preferred approach, clients MUST send a request to a server to allocate a range of internal identifiers for their exclusive use by using RopGetLocalReplicaIds. Clients can then assign these IDs to any new folders or messages within their local replica and communicate these assignments back when performing upload by using ICS RopSyncrhonizationImportHierarchyChange (as specified in section 2.2.3.2.4.3) or RopSyncrhonizationImportMessageChange (as specified in section 2.2.3.2.4.2). Note that these IDs MUST NOT be used for change numbers. Clients MUST generate foreign identifiers to identify changes to objects in the replica, as specified in section 3.3.1.1.3. This mechanism is being serviced by two ROPs, RopGetLocalReplicaIds (as specified in section 2.2.3.2.4.7) and RopSetLocalReplicaMidsetDeleted (as specified in section 2.2.3.2.4.8). To help compression of IDSETs and to alleviate fragmentation of the deleted item list, if a server maintains an IDSET for a folder, clients SHOULD assign consecutive IDs from the allocated range to messages within the same folder. One possible mechanism to achieve this is to allocate a contiguous subset of allocated IDs to each folder. Clients MUST report IDs assigned to objects in a client replica that were deleted without ever uploaded through RopSynchronizationImportDeletes. Clients MUST report ranges of server-allocated IDs, which will never be used for any messages in a folder, through RopSetLocalReplicaMidsetDeleted. For an example, see section 3.3.4.2.2.8. Use Online Mode ROPs
Other Local Events None. Client Details This section provides client-specific details related to bulk data transfer. The Mailbox Synchronization Protocol Specification [MS-OXCSYNC] also contains important details related to bulk data transfer. Abstract Data Object and Change Identification The following three alternative mechanisms are available to clients that need to create objects in their local replica without having immediate contact with the server to upload the differences. This is also known as working offline. Client-Assigned Internal Identifiers When this most preferred approach, clients MUST send a request to a server to allocate a range of internal identifiers for their exclusive use by using RopGetLocalReplicaIds. Clients can then assign these IDs to any new folders or messages within their local replica and communicate these assignments back when performing ICS upload by using RopSyncrhonizationImportHierarchyChange (as specified in section 2.2.3.2.4.3) or RopSyncrhonizationImportMessageChange (as specified in section 2.2.3.2.4.2). Note that these IDs MUST NOT be used for change numbers. Clients MUST generate foreign identifiers to identify changes to objects in the replica, as specified in section 3.3.1.1.3. This mechanism is being serviced by two ROPs, RopGetLocalReplicaIds (as specified in section 2.2.3.2.4.7) and RopSetLocalReplicaMidsetDeleted (as specified in section 2.2.3.2.4.8). To help compression of IDSETs and to alleviate fragmentation of the deleted item list, if a server maintains an IDSET for a folder, clients SHOULD assign consecutive IDs from the allocated range to messages within the same folder. One possible mechanism to achieve this is to allocate a contiguous subset of allocated IDs to each folder. Clients MUST report IDs assigned to objects in a client replica that were deleted without ever uploaded through RopSynchronizationImportDeletes. Clients MUST report ranges of server-allocated IDs, which will never be used for any messages in a folder, through RopSetLocalReplicaMidsetDeleted. For an example, see section 3.3.4.2.2.8. Use Online Mode ROPs