Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:web_api:v3:syncing [2019/03/10 16:57] – dstillman | dev:web_api:v3:syncing [2019/03/19 05:38] – [Sync Properties] dstillman | ||
---|---|---|---|
Line 14: | Line 14: | ||
* A version number for each library | * A version number for each library | ||
* A version number and a boolean '' | * A version number and a boolean '' | ||
- | * A flag indicating that a downloaded | + | * A list of downloaded |
===== Version Numbers ===== | ===== Version Numbers ===== | ||
Line 219: | Line 219: | ||
- Treat the error as fatal and stop the sync without updating the local library version | - Treat the error as fatal and stop the sync without updating the local library version | ||
- | - Mark the object | + | - Add the object |
When processing a set of objects, it may be helpful to maintain a process queue for the sync run and move failing objects to the end of the queue in case they depend on other objects being retrieved. (In many cases, it's possible to sort objects beforehand to avoid such errors, such as by sorting parent collections before subcollections.) If a loop of the process queue completes without any objects being successfully processed, stop the sync. | When processing a set of objects, it may be helpful to maintain a process queue for the sync run and move failing objects to the end of the queue in case they depend on other objects being retrieved. (In many cases, it's possible to sort objects beforehand to avoid such errors, such as by sorting parent collections before subcollections.) If a loop of the process queue completes without any objects being successfully processed, stop the sync. |