Performance of formHandler

This script was created with performance in mind. But it is impossible to
keep increasing functionality without loosing performance.

However formHandler is the first script that is so modular, that it is
possible to leave out modules in the configuration to tune the performance.
This file will describe some possibilities to boost the performance.

When the script was tested on my pentium 166 it took tops 10-20 seconds
(meanwhile doing a dist-upgrade of debian) to execute the script. If you
have a pentium III or higher you probably don't need to read this file,
because execution times will stay below 2 seconds.

0. In development

Since release 1.6a the number of runlevels is brought down to 30 (was 100).
The first 10 are not dynamically configurable, so the next 10 (10-19) are
used for setting and checking things. The last 10 are used for executing
the mail-functions, display, etc. This does not mean that less modules can
be used, because on every level an infinite number of modules can be
executed. But it may be harder to give a specific order in which the
modules must be executed. I'm leaving out the possibility here to decrease
the number of runlevels, because that is relatively hard to do.

1. Turn of AUTO_CONFIG

First performance tuning can be done by creating an option in the
configfile or in the form that specifies the modules that need to be loaded
in. The optionname may be: config, modules of extra_modules (see
config.mod.php). When using a form, create a hidden input field that has a
value like this: "required:fieldcheck".
The names given are the names of the files (with extension .mod.php).
In configfile.inc.php you can now change AUTO_CONFIG into false. This
option (when true) reads all .def.xml files and creates the modules if some
options specified in the xml-file exist.

2. Consider the use of each module

Every module is dynamically loaded even without AUTO_CONFIG. If you leave
out a module, it means that code isn't even read in. When a module is read
in, automatically some code is executed even though the rest of the module
isn't used.

3. The bigger the form ...

If you have more fields used in your form (hidden or user-input fields) the
more information the script needs to store and the more checks need to be
performed by the modules.

4. The bigger the configfile ...

Every option in the configfile is added to the information stored from the
form. So see 3.

5. Turn off debugging

In the configfile.inc.php you can change the debug.mes.php into the
debugdummy.mes.php. This will totally turn off debugging.