Download as PDF, PPTX
Uploaded byMake School
Client Server Synchronization iOS
The document discusses client-server synchronization for a trip planner application. It describes tracking changes made by the client so they can be sent to the server, and checking the server for updates. The client needs to find all objects updated or created locally since the last sync, and deletions not yet synced, to generate sync requests. When syncing from the server, it will delete local trips that don't exist on the server, and potentially update trips that differ.
Client Server Synchronization iOS
- 2.
- 3. AGENDA Basics of ClientServer Synchronization Synchronization for Trip Planner Architecture Overview
- 4. STRETCH GOAL! Remember! Thisstep is a stretch goal of the Trip Planner project. We don’t expect everyone to finish completely.
- 5. BASICS OF CLIENTSERVER SYNCHRONIZATION
- 6. BASICS OF CLIENTSERVER SYNCHRONIZATION Main Goal: Client and server should (almost always) have the same data Changes from the client need to be sent to the server Client needs to check server for updated information frequently
- 7. TRACKING UNSYNCED CLIENT CHANGES Changesto local data need to be tracked - need to remember which data has been sent to server successfully and which not Need to track new, updated and deleted data
- 8. DESIGNING THE SYNCHRONIZATION FORTRIP PLANNER
- 9. TRACKING UNSYNCED CLIENT CHANGES Potentialsolution: • using a lastUpdate timestamp to check which objects changed since last server sync • using a serverIdentifier to store server ID and to check which objects are new locally • keep a list of deleted objects that need to be synced
- 10. SYNCING CHANGES TOTHE SERVER Find all: • Objects that updated since last synchronization • Objects that have been created since last synchronization • Deletions that haven’t been synchronized yet → Generate network request(s) to sync these changes
- 11. SYNCING CHANGES FROM THESERVER Download trips from the server: • find trips that exist locally, with server identifier but don’t exist on server → delete them • find trips that exist locally and are different in server response → compare which entry is newer and potentially update local trip
- 12. ADVANCED APPROACH Instead ofdownloading all trips from server, only download the ones the client doesn’t know about yet (this is beyond the scope of the project)
- 13.
- 14. ARCHITECTURE OVERVIEW Synchronizer API Client Authentication CoreData Client Keychain Remaining App
- 15.
- 16. ADDITIONAL RESOURCES Objc.io: DataSynchronization Objc.io: A Sync Case Study