Client-server synchronization pattern / algorithm?

by

You should look at how distributed change management works. Look at SVN, CVS and other repositories that manage deltas work.

You have several use cases.

  • Synchronize changes. Your change-log (or delta history) approach looks good for this. Clients send their deltas to the server; server consolidates and distributes the deltas to the clients. This is the typical case. Databases call this “transaction replication”.

  • Client has lost synchronization. Either through a backup/restore or because of a bug. In this case, the client needs to get the current state from the server without going through the deltas. This is a copy from master to detail, deltas and performance be damned. It’s a one-time thing; the client is broken; don’t try to optimize this, just implement a reliable copy.

  • Client is suspicious. In this case, you need to compare client against server to determine if the client is up-to-date and needs any deltas.

You should follow the database (and SVN) design pattern of sequentially numbering every change. That way a client can make a trivial request (“What revision should I have?”) before attempting to synchronize. And even then, the query (“All deltas since 2149”) is delightfully simple for the client and server to process.

More Related Contents:

  1. Synchronizing client-server databases
  2. Sending POST data in Android
  3. Java socket API: How to tell if a connection has been closed?
  4. Sending files using POST with HttpURLConnection
  5. How do multiple clients connect simultaneously to one port, say 80, on a server? [duplicate]
  6. How to Sync iPhone Core Data with web server, and then push to other devices? [closed]
  7. TCP Client to Server communication
  8. why do we use 10.0.2.2 to connect to local web server instead of using computer ip address in android client
  9. How to share semaphores between processes using shared memory
  10. How to pass a parameter to html?
  11. How do I run my application as superuser from Eclipse?
  12. Checking for multiple asynchronous responses from Alamofire and Swift
  13. Best way to synchronize local HTML5 DB (WebSQL Storage, SQLite) with a server (2 way sync) [closed]
  14. Does the port change when a server accepts a TCP connection?
  15. close() is not closing socket properly
  16. java.io.InvalidClassException: local class incompatible:
  17. Is there a WebSocket client implemented for Python? [closed]
  18. How to store data in S3 and allow user access in a secure way with rails API / iOS client?
  19. Multithreading Socket communication Client/Server
  20. Intercept Tkinter “Exit” command?
  21. Chart data exported to an Apps Script webapp is null
  22. ReactJS server-side rendering vs client-side rendering
  23. Avoid caching of the http responses
  24. How to keep the android client connected to the server even on activity changes and send data to server?
  25. How many clients can an http-server handle?
  26. How do I obtain the latency between server and client in C#?
  27. Very large HTTP request vs many small requests
  28. Reliable way of generating unique hardware ID
  29. Maximum number of concurrent connections on a single port (socket) of Server

Leave a Comment