![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Warning: this is the first in a series of technical entries regarding the details of data synchronisation. Look away if you don’t care.
I’ve been working on and off over the past six months at including offline capabilities in our web-based athlete management system. The idea is that a coach or a doctor should be able to unplug their machine from the network, go out to a training camp or on a scouting trip and use the system completely as normal, then come back and push the changes they’ve made into the main system and pull back any changes made by other people in the meantime.
The obvious technology to use, given we’re in a .NET environment, is the new Microsoft Sync Services framework based around SQL Server CE. Plenty of examples around - and now it's all got a wizard, including bidirectional synchronization should be as easy as ABC: click through the wizard, add a web service on one end and a reference on the other, run the autogen upgrade scripts on your server database, and go!
( Reality is never so simple. )
Coming up: what the ClientSyncProvider doco should tell you, and a short history of SyncAnchor.
I’ve been working on and off over the past six months at including offline capabilities in our web-based athlete management system. The idea is that a coach or a doctor should be able to unplug their machine from the network, go out to a training camp or on a scouting trip and use the system completely as normal, then come back and push the changes they’ve made into the main system and pull back any changes made by other people in the meantime.
The obvious technology to use, given we’re in a .NET environment, is the new Microsoft Sync Services framework based around SQL Server CE. Plenty of examples around - and now it's all got a wizard, including bidirectional synchronization should be as easy as ABC: click through the wizard, add a web service on one end and a reference on the other, run the autogen upgrade scripts on your server database, and go!
( Reality is never so simple. )
Coming up: what the ClientSyncProvider doco should tell you, and a short history of SyncAnchor.
