Product Documentation

FairCom mtPro

Previous Topic

Next Topic

Client Side

The FairCom DB Client/Server model is ideal for most applications. You can build the client side library to include in your application. Multiple options are available as shown below.

client side

Client Side Library Options

  • Multi Threaded Client (default) - Choose this for most uses. This is the default library included with all FairCom DB installations.
  • Single Threaded Client - Choose this client library model if you only require a single thread per user.
  • Single Threaded Client (LOCLIB) - Choose this unique client library model if you also require a local standalone database in addition to a remote server. The standalone library is a single user library supporting transaction processing. The command line mtmake utility has additional options should you need an alternative standalone library model.

Communications Protocols

Multiple client/server communications options are available. The default FairCom DB database engine supports TCP/IP and Shared Memory protocols as installed.

  • TCP/IP + Shared Memory (default) - This default option is the most reliable and universal communication standard available. Shared Memory will be used if your application runs on the same host machine as the FairCom DB database engine, otherwise TCP/IP will be used.
  • Shared Memory Only - Choose this option if your application runs on the same host machine as the FairCom DB database engine.
  • TCP/IPv6 - Select this option for TCP/IP using IPv6.

Client Side Library Type

  • Dynamic Link (DLL) - The dynamic link library offers the most flexibility for many applications and is the FairCom DB default. This makes it very easy to switch the FairCom DB client library should you wish to update, or change options in the future without recompiling your entire application code.
  • Static Link (default) - Choose the static option if you wish to link the FairCom DB client library directly to your application code.

TOCIndex