Getting started with php and InterBase Page 2

Getting and installing InterBase

InterBase 6.01 can be downloaded here:
http://www.borland.com/devsupport/interbase/opensource/

For Linux, two versions exist:

• The Classic Server
• The Super Server

The Classic Server

(From the website)

Prior to version V4.1.0 of InterBase, the server was designed in a way that
is now called the Classic Architecture.
In this design, each client connection to the server spawns a separate process.
Each process does I/O directly to the database files, and negotiates access to the database files
by interprocess communication methods like semaphores.
Each of these server processes also keeps a cache of database pages in its
own address space.
When a connection terminates, the process that was spawned for it also
terminates. The process’ termination causes the memory that it allocated to be
freed.

The Super Server

(From the website)

Version V4.2.X introduced a new server model called “superserver”.
The superserver model is a thread-based approach. This means that there is one
process and a pool of threads to handle remote connections. So, for each
remote connection threads are used to manage the connection, opposed to a new
process in the classic model. The memory deallocation problem becomes more of
an issue with the superserver model because of the server process never
terminating. When a connection terminates the associated thread is placed back
in the thread pool or terminated. However, neither of these actions affects
the memory allocated, because memory allocation is process-based not thread-
based.

In Linux, the super-server-rpm (InterBaseSS_LI-V6.0-1.i386.rpm) always worked fine for me.

For Windows, I chose InterBase_WI-V6.0.1-server.ZIP.

According to a reply from the ibsupport mailing-list, no security patches are needed, they
are already included in 6.01.