AFS Integration Guide

Reference Guide

CGI, or Common Gateway Interface, is the historical standard for interfacing web servers and application binaries. It is widely used and robust. However it may lead to performance issues since each query requires the web server to create a new process (typically a process running acp, search, content or click when using AFS). The process is in charge of building the reply — once this task is done, the process ends.

CGI implies an overhead for each query since:

  • The operating system must create a new process for each query. These processes will have a very short lifespan (usually less than a second). Process creation and destruction on a large scale (several millions of cycles per day on heavily loaded servers) can be very costly and reduce the benefits of resource reuse techniques (like in-memory caching).
  • The binaries have no persistence, because each query they need to read the (same) configuration files, initialize (the same) helper libraries.