Classes needed by the Sync Engine providers: XPD621
This section identifies the basic classes that are used when providing a new Sync Engine and SyncService. This is not an exhaustive list of all classes that could be used, but rather a list of the classes referred to in the following sections. Additional classes may be used in other circumstances. Refer to the Javadoc for more detailed information on the classes and the methods provided.
Creating the Sync Engine: XPD621
The Sync Engine is the code that actually performs the synchronization of the database between a source and a target. The Sync Engine has a set of data types or resources that it understands how to synchronize.
Implementing SUSyncData: XPD621
The SUSyncData implementation is the store for engine specific data for a specific synchronization unit or task.
Implementing SyncUnit: XPD621
As discussed previously, the SyncUnit implementation is primarily a wrapper around the data associated with a synchronization "task". It also serves as the conduit to the SUSyncData implementation, which stores the engine specific data.
Implementing SyncService: XPD621
The SyncService is the chunk of code that controls the interaction between the Synchronization UI and the Sync Manager, and the Sync Engine.
Enabling users to customize the synchronization task: XPD621
The TypeService defines the SyncUnit implementation class that represents the synchronization task. If the definition of the synchronization task (SyncUnit) contains options that you want to be settable by users of the Synchronization UI, you can define property pages to make those options available. If a property page is defined for a specific SyncUnit, then the Options menu becomes active for the particular SyncUnit.