a1ce85decb
Previously, objects were first downloaded and saved to the sync cache, which was then processed separately to create/update local objects. This meant that a server bug could result in invalid data in the sync cache that would never be processed. Now, objects are saved as they're downloaded and only added to the sync cache after being successfully saved. The keys of objects that fail are added to a queue, and those objects are refetched and retried on a backoff schedule or when a new client version is installed (in case of a client bug or a client with outdated data model support). An alternative would be to save to the sync cache first and evict objects that fail and add them to the queue, but that requires more complicated logic, and it probably makes more sense just to buffer a few downloads ahead so that processing is never waiting for downloads to finish. |
||
|---|---|---|
| .. | ||
| schema | ||
| tinymce | ||
| bluebird.js | ||
| concurrentCaller.js | ||
| config.js | ||
| csl-validator.js | ||
| hide.vbs | ||
| pathparser.js | ||
| redirect.sh | ||
| redirect.vbs | ||