MrRooni
commented
11 years ago This is true, which is why we recommend that devices periodically upload the whole store file so that other devices have fewer change sets to apply when setting up syncing for the first time. You can use the TICDSDocumentSyncManagerDelegate method:
/** Invoked to ask the delegate whether the document sync manager should automatically initiate a Whole Store Upload at registration.
@param aSyncManager The document sync manager object that sent the message.
@return `YES` if the sync manager should initiate the upload, otherwise `NO`. */
- (BOOL)documentSyncManagerShouldUploadWholeStoreAfterDocumentRegistration:(TICDSDocumentSyncManager *)documentSyncManager;to tell the document sync manager that it should upload the whole store.
ghost
[update, 2013-01-29] As per the conversation below, uploading large whole store files can be problematic because the user shouldn't be allowed to update the store while the upload is happening. Perhaps we can copy the store off to a temp location before kicking off the upload.
[original message] After downloading whole data store, local device needs to apply all previous changes
When the user uploads the whole data store on device A (say, their iPhone), it uploads a copy of the core data store, and as they make changes it begins to upload change sets. However, when the user downloads the data store onto device B (say, their iPad), it has to first download the initial copy of the whole data store, and then successively apply all of the change sets. This is very time consuming, especially if there is a time lag between when device A first uploaded the data store, and when device B downloads it, because there can be many change sets.