Comparisons between IBM Sync Client C-API Version 8.1 and Version 7.2

This section summarizes the major changes made to the IBM Sync Client C-API in Version 8.1:

Three handles are now available: service, configuration, and engine. (If you do not want to perform synchronizations, you do not need to open the sync engine handle.)
The preferences in the IBM Sunc Client C-API Version 8.1 are not persistent, and some preferences, which actually are essential information have been removed. For example, the host name, port, user name, and password in the old isyncSetPref function are now the required parameters in the iscOpenService function for opening a service handle.
The synchronization mode is now implicit to the application, and the synchronization mode parameter is no longer required when invoking a synchronization.
The interface to the synchronization listener is now event based. Event structures that contain event information are now passed to the application.
The synchronization status of a subscription set (from its last synchronization) is persistent and can be inquired afterward.
The default listener has been removed. When a default action for an event is needed, the application simply returns the ISCRTNCB_Default code.
DB2e Everyplace now supports data encryption to protect the table which contain sensitive data. When developing a sync client application to synchronize encrypted tables, you can implement (in the listener) the query from the sync engine for the DB2 Everyplace user name and password.
Rejected records (including records with conflicts or illegal operations) are now passed to the application through the listener.
The log file (LOGDB-ISYNC) is now managed by the application. That is, the Version 8.1 synchronization engine no longer generates the log file (LOGDB-ISYN) in a natively language as in version 7.2.1. Instead, for service purpose, the synchronization engine will generate a trace file (TRACE-ISYN), which is in English only
The IBM Sync Client engine stores all files (including the configuration, trace file, data, and preferences (if applicable) in one directory:
- On Windows CE^(R) operating systems: \ (root directory)
- On EPOC operating systems: C:\Systems\Data\ISync\
- On Palm operating systems: the main memory
- On other operating systems: the current directory
The functionality of the IBM Sync Client API Version 7.2.1 is still supported through an API wrapper (the isynce library), which will handle the backward compatibility of the API. The API wrapper also generates the log file (LOGDB-ISYN) in native languages in the same directory as in Version 7.2.1, that is:
- On Windows CE^(R) operating systems: \Progran Files\ISync\
- On EPOC operating systems: C:\Systems\Apps\ISync\
- On Palm operating systems: the main memory
- On other operating systems: the current directory
In addition, the ISYNCOPTION_SkipConfig and ISYNCOPTION_UseAppSignature options will not work with the isyncGo and isyncSetSyncMoe functions.
주:
The API wrapper (isynce) library does need to be installed if choose to use IBM Sync Client API Version 8.1.

표 114 lists the major differences between the functions in the IBM Sync Client C-API Version 8.1 and the IBM Sync Client Version 7.2.

표 114. The IBM Sync Client C-API Version 8.1 and Version 7.2 comparison

Version 8.1	Version 7.2	Remarks
`iscGetVersion`	`isyncGetVersion`	No handles needed in `iscGetVersion`.
`iscServiceOpen` `iscConfigOpeniscEngineOpen`	`isyncOpen`	Need to open three handles. Host, port, user name, and password are specified in `iscServiceOpen` and are not persistent.
`iscServiceClose` `iscConfigClose` `iscEngineClose`	`isyncClose`	Need to close three handles.
`iscEngineSetListener`	`isyncSetListener`	The listener prototype and interface have changed.
(None)	`isyncDefaultListener`	No more external default listener. For default event handling, returns the ISCRTNCB_Default code.
`iscEngineSetPref` `iscEngineGetPref`	`isyncSetPref` `isyncGetPref`	Only two preferences (trace and timeout) are required. These preferences are not persistent.
`iscEngineSync` `iscEngineSyncConfig`	`isyncGo`	Sync mode is no longer required. Can update the configuration only with `iscEngineSyncConfig`.
`iscConfigEnableSubsSet` `iscConfigDisableSubsSet` `iscConfigResetSubsSet`	`isyncSetSyncMode`	No more general sync mode setting. Synchronization of a subscription set can be skipped (disabled) by `iscConfigDisableSubsSet`.
`iscConfigOpenCursor` `iscConfigCloseCursor` `iscConfigGetNextSubsSet` `iscConfigSubsSetIsEnabled` `iscConfigSubsSetIsReset`	`isyncGetFirstApp` `isyncGetNextApp`	Opens a cursor before iterating subscription sets. A subscription-set ID is needed to query a subscription set.
`iscEngineGetInfo` `iscConfigPurge` `iscConfigGetSubsSetStatus`		New C-APIs in Version 8.1.

Related concepts

The sample Sync Client C/C++ application

Related tasks

Developing DB2 Everyplace Sync Client applications using C/C++

Related reference