|
|
|
We begin by reviewing a non-server FairCom DB application. To implement a database, the program uses FairCom DB functions. The FairCom DB library is included at link time to resolve these functions, and thus, the database logic in FairCom DB becomes part of the executable module.
The application code for a client/server implementation need not change, although the FairCom Server does support extended capabilities. The program still takes advantage of the same functions used for standalone FairCom DB applications.
Instead of linking with the traditional FairCom DB library, the client/server application must be linked with a FairCom Server client communications library. The communications library resolves the same FairCom DB functions, but instead of including the database I/O logic within the executable, communication logic used to request database I/O with the FairCom Server becomes part of the executable. Because the client/server communication logic is smaller than the non-server database I/O logic, the resulting executable is smaller.
The FairCom Server includes a number of client communication libraries. The appropriate library to use depends on the operating system and the supported communication method within that environment.
