The original support that Palm provided for
mirror-image synchronization was an
MFC (Microsoft Foundation
Classes) Conduit framework. These classes are sometimes called
because of the filenames in which they are located.
These classes worked very well for the standard conduits (for example, the conduits for Palm Desktop are built with the MFC Conduit framework). There are some limitations that make them more difficult for third parties to use, however:
First, they do require MFC, which means that your conduit must provide information on what version of MFC is used. This can make debugging somewhat more difficult.
Second, the file format they write is MFC-serialized objects; that’s handy for Palm Desktop, since Palm Desktop is an MFC-application. It is quite difficult to write other formats, however.
In addition, there’s no easy way to port a conduit based on the MFC Conduit framework to the Mac OS.
For these reasons, we don’t recommend using this framework.