Generic Conduit Classes
There are eight classes that affect your use of Generic conduit. As might be expected, each has a different responsibility. Figure 16-1 shows the inheritance relationship.

Figure 16-1. Inheritance relationship of Generic conduit classes
Table 16-4 contains a quick look at each class, in the order we discuss them in this chapter.
Table 16-4. Generic conduit classes
|
Class |
What it does |
Use |
|---|---|---|
|
|
Represents a record (including attributes, ID, category number, length, and a pointer to data). |
As is |
|
|
Represents a category on the handheld. |
As is |
|
|
Represents a set of categories. |
As is |
|
|
Defines database methods for iterating, adding and deleting records, and so on. |
Classes derived from |
|
|
Subclass of CPDbBaseMgr; implements those routines by using Sync Manager. |
As is |
|
|
Subclass of CPDbBaseMgr; implements the CDbManager member functions for a file on the desktop. |
Derive own class from |
|
|
Reports errors to the sync log. |
As is |
|
|
Handles the sync logic and control flow. |
Derive own class from |
Now let’s examine each class in detail.
CPalmRecord
This represents a Palm record; it stores attributes, a unique ID, a
category number, a record length, and a pointer to the raw record
data. The CPalmRecord, just like a record on the handheld, has no concept of fields; to ...