Each file extension is associated with a Content Generator (CG) ALP module and
settings for it. Select a file extension and click Edit to edit the settings
for the CG associated with it or click Remove to remove the association.
If the association is removed it may still be active if it is specified in the
default ALP settings. This behavior is kept for compatibility with the previous
ALP versions.
Type the file extension you want to configure and then select the ALP Content Generator module to be associated with it. Note If you are using ASP pages in this application do NOT replace the .ASA files association with other settings. Such a replacement may lead to strange and unexpected results.
Select an ALP module to handle the specified extension. After clicking the Add button the default settings for this module will be applied and you will be allowed to edit them.
Restore the default ALP application settings. All the edited settings will be lost. This is good if you have mistaken the ALP application configuration and you want to start over.
Deleting the application will remove the alp.application file from this directory.
No other files will be affected. The directory will remain part of any parent application
defined (explicitly or implicitly). See the ALP documentation for more information.
Brief information
Each ALP virtual site starts implicitly ALP application with the default ALP
application settings. If there is no alp.application file ALP will use the defaults.
If in any directory alp.application file is present, then this directory its subfolders
will act as one application unless some of the subdirectories does not contain alp.application
file in turn. In which case this folder will start new application - issolated from the
parent application. This behavior is very similar to the IIS behavior and differs only in
the way it is specified. In ALP the alp.application file define the application borders in
the file system, while in IIS these settings are keept in external storage.
The files not handled by explicitly specified ALP modules are processed by the default ALP Content Generator (called RawSpool). This module supports some settings that can be configured on this page.
One site object is created for each ALP site when the site is entered for the first time.
The object will expire if it is not accessed for the specified period. In the current version
no ALP modules use site objects.
ALP supports internally global object storages for the modules handling the requests.
The expiration is controlled by ALP and not by the modules. Site storage has no equivalent in
other WEB servers and engines, Application is equivalent to the ASP application in IIS. Session
is equivalent to the ASP session. Note that not all the modules use all the global object storages.
One application object is created for each ALP application when the it is entered for the first time. The object will expire if it is not accessed for the specified period. In the current version ASP pages and RAW scripts use these objects. The other ALP modules will not be affected.
One session object is created when the user enters for the first time certain ALP applciation. In ALP the difference between the application and session objects is not considerable. However for compatibility reasons the session objects should have short expiration time (usually 20 - 60 min.).
ALP buffers the output made by any module. This allows ALP to clear the output in certain situations or create temporary files if requested. The size of the output buffer limits the maximum content size that can be transfered through one ALP request/response sequence. For applications that use mostly HTML/images content 1MB buffer should be more than enough. Larger buffers may be needed if the application generates huge data.