Microsoft Sync Framework - How does bidirectional synchronization work?

Question

I have two clients A and B. Both clients have the same synchronized local data caches.

If client A does offline editing for record X, and then client B also autonomously edits record X and synchronizes with the server when client A synchronizes with the server, the change made by client B is not reflected, and the number of bidirectional synchronization allows two clients to synchronize correctly with server.

Other than that, my sync app is great for deleting, adding changes, etc. These are only simultaneous autonomous changes that destroy integrity.

I am using SQL 2005 (using SQL scripts to support synchronization)

Is there any resource that explains the nuts and bolts of how the synchronization structure works and how it decides when to synchronize recordings?

Answer 1

Is there any resource that explains nuts and bolts, how the synchronization structure really works and how it decides when to synchronize recordings?

Have you looked at the Sync Framework specification ? In addition, Steve Lasker has some helpful tips on OCS and the timing structure. He was largely the main driving force behind OCS and SF, although he has now moved to Cloud.