The documentation covers all synch framework components, which include the core components, file harmonizing provider, database sync providers and web feed sync components. The program documentation offers an introduction and a set of reference and how-to topics to help one quickly comprehend and use it productively.
Developers could create a robust system that integrates an app with any type of data storage over any network and protocol. Through the tool, one could be certain that all info stores have the correct input and concurrent updates are handled appropriately.
The following are the components that could be used to make synchronization providers for any particular store kind.
1.Metadata storage service - could be used for storing synch metadata in a lightweight store. It contains the information necessary required for coordination. Both managed and unmanaged interfaces offer access to metadata services.
2. Runtime - controls the synch session object, communicates with client apps and interacts with vendors on behalf of the client. One could begin, cancel or host a session and resolve errors and conflicts during synchronization. Managed and unmanaged interfaces offer runtime access.
3. Ado.net services - could be used for synchronizing databases for collaborative and offline scenarios.
4. File systems - could be used for synchronizing folders and files in a file system.
5. Feed Sync - can be utilized to accord Atom and RSS feeds with information in a local storage.
A participant is a service or device that could concur with other systems using the Microsoft framework. It would synchronize input among participants of different functionality. It supports the following types of participants.
1. Full participant - locally hosts the runtime and stores metadata.
2. Proxy - would start synching from a remote provider through loyally handling calls and forwarding them to the remote provider.
3. Partial - could store metadata, but is unable to process it. It depends on the full participant for runtime services and start of integration.
4. Simple participant - could not keep metadata, cannot host runtime. It will depend on the full participant to perform everything.
The framework would be handy for maintaining specific stores with the right data. For instance, this could be used for synching public contacts in address-book store as well as outlook information storage. Moreover, it features technologies and tools which enable sharing, roaming and taking information offline. It's simple in theory and could be crucial to the success of any organization. It benefits a wide range of apps that need data synchronization. For example, business apps that share statistic like documents could use the tool to ensure that all members of the team receive document updates. Moreover, it also ensures that conflicts on current upgrades are taken care of appropriately.