Data synchronization race conditions? about backbone.dualstorage HOT 1 CLOSED

1. The client probably wins, but you could teach the server to recognize outdated updates, perhaps by checking a timestamp, according to your app's business rules. In more concrete terms, when syncDirtyAndDestroyed syncs successfully, it will send create/update/destroy requests to the server as if they had just been performed.
2. fetch, AKA 'read', will load data from localStorage exclusively while there are any dirty or destroyed records. See https://github.com/nilbus/Backbone.dualStorage/blob/master/backbone.dualstorage.coffee#L249.
3. For fetches, it looks like the entire local store for the collection/model gets cleared out after every successful fetch, which includes dirty and destroyed records. Before the syncDirtyAndDestroyed callback returns (while the ajax requests wait), any fetch on dirty records will return the data in localStorage.

On the topic of synchronicity issues, please be aware of #76 and #35, which has a workaround committed to master (cd17ff2).

The behavior of clearing the store when fetching a model seems like a bug to me. Opened #78 to address this.

from backbone.dualstorage.