Previous Topic

Next Topic

Stand-alone Single-user Model

The Stand-alone Single-user Model is part of FairCom’s non-client/server architecture offering both single-user capabilities, meaning only one process may open a given file.

With the Stand-alone Single-user Model, your application is linked with the c-tree Plus database engine that supplies a Function API in the form of a static library, DLL, or shared library. All file related operations are done through the c-tree Plus API, which ultimately utilizes your compiler’s runtime library routines, (i.e., open, close, read, write, etc.). The file I/O, or disk I/O as illustrated in the diagram, is cached to improve performance.

Applications designed to have only one user accessing files at a time can use this non-server single user mode. All of the capabilities of c-tree Plus are supported, with the exception of file security control and encryption. The c-tree Plus code will be linked as a part of your application. The developer can specify the amount of memory to be used for file buffering, which can have a significant effect on the speed of the system. Full source code is included, which allows the developer to move the product to any operating environment that supports the C language. The caching offered by the single-user model provides better throughput than the multi-user model.

This model provides an easy migration path to the client/server model with features such as: robust data concurrency, multi-user data integrity through on-line Transaction Processing (OLTP), and all of the other features offered by the client/server model.

Benefits

  • Self-contained (Stand Alone) executable.
  • Accelerated performance with data and index cache.
  • Transaction processing support.
  • Flexible API with powerful fixed and variable length record support.
  • Complete source code included for maximum control and portability.
  • Compile as a static library, DLL, or Unix Shared Library.
  • Mac libraries support Carbon API

Considerations

  • No support for multi-user file access.
  • Extra network traffic when accessing a network file server, especially with large files.