FairCom ISAM for C

Operational Models

This chapter describes the various FairCom DB operational models, how to move files between operational models, and how to change the operational model for your application. FairCom DB installation is described in Chapter 1 “Installation” of the Quick Start and Product Overview Guide, along with steps for integrating your application with FairCom DB and helpful hints for getting started.

FairCom DB can be configured to operate in a variety of ways, which are referred to as operational models. The features that vary from one model to another are single-user versus multi-user access, support of a database server, support of higher level functions such as transaction processing and file mirroring, and availability of source code. This section provides a brief overview of the available models.

All configurations have been designed with the developer in mind, allowing you to switch models by simply re-compiling with FairCom’s m-tree make system.

The supported operational models are:

1. Standard Client/Server Model - client/server.
2. Standalone Single-User Model.
3. Standalone Multi-User Model.
4. LOCLIB Model - client/server model with client side local library support.
5. Multi-Threaded Standalone Model - Standalone Multi-user multi-threading support.
6. CTUSER Server Model - add user functionality to the Server side.
7. Bound Server Model - bind the FairCom Server engine into your application
8. Custom Server Model - add your own logic to the FairCom Server.

In This Chapter Standard Client/Server Model Standalone Single-User Model Standalone Multi-User Model LOCLIB Model Multi-Threaded Standalone Model CTUSER Server Model Bound Server Model Custom Server Model Operational Model Considerations