Nuts and Bolts
If you stepped through the SimpleDB CDK sample
project, you saw that the VB code manipulated the Palm
device’s databases and records using COM objects.
Let’s dig a little deeper into the HotSync
architecture to see how a conduit communicates with the Palm device.
Recall from Figure 4-1 that the COM Sync Suite provides the interface to the HotSync manager and the Palm device.
The Sync Suite itself has several layers to isolate its interface from the underlying details of the HotSync application and to support both VB/COM and C/C++ conduits. This layered approach frees the VB programmer from worrying about messy details such as which serial port the HotSync manager is using to communicate with the Palm device.
To simplify conduit development, the Sync Suite provides COM objects and classes that encapsulate the HotSync manager, the user, and databases on the Palm device. A utility class is provided to handle things like Motorola byte ordering and unique record identifiers.[30] These classes and their relationships are shown in Figure 4-5.

Figure 4-5. Sync Suite class hierarchy
There are VB projects in the CDK that cover these objects and interfaces. Rather than enumerate all of them here, we will discuss the major ones we encounter as we develop our simple conduit. Once you understand the framework, you can use the VB Object Browser and the Conduit Reference manual to ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access