This is my final post related to Oracle Offline Persistence Toolkit. I will show simple example, which explains how to apply server changes, if data conflict comes up. Read previous post about - Oracle Offline Persistence Toolkit - Submitting Client Changes.
To apply server changes is easier, than to apply client changes. You need to remove failed request from sync queue and fetch server data to client by key.
Example of data conflict during sync:
User decides to cancel his changes and bring data from the server. GET is executed to fetch latest data and push it to the client:
In JS code, first of all we remove request from sync queue, in promise we read key value for that request and then refetch data:
Download sample code from GitHub repository.
To apply server changes is easier, than to apply client changes. You need to remove failed request from sync queue and fetch server data to client by key.
Example of data conflict during sync:
User decides to cancel his changes and bring data from the server. GET is executed to fetch latest data and push it to the client:
In JS code, first of all we remove request from sync queue, in promise we read key value for that request and then refetch data:
Download sample code from GitHub repository.
No comments:
Post a Comment