forked from superzanti/ServerSync
-
Notifications
You must be signed in to change notification settings - Fork 0
Project update sync process
R edited this page Mar 3, 2020
·
2 revisions
Benefits
- Lower memory use as we are working on a file by file basis rather than holding lists
Drawbacks
- Needs multiple client file passes to sync everything
Gist
- The client starts a sync process with the server
- The server sends a series of questions to the client asking if it has various files
- The client deletes any remaining files
Benefits
- Single sync process, only need to fetch the clients files once
Drawbacks
- Relatively complicated dialog between the client and server for file sync
Could potentially combine both approaches and do an early delete phase to get rid of client files that don't exist on the server.