Since you will be creating HTML pages that contain Tcl scripts, you will need to specify which pages the server will need to parse for Tcl commands and process.
The following table describes the parameters that can be set within the ADP section of the configuration file:
The Map parameter specifies which pages the server will parse. You can specify a file extension (such as /*.adp) or a directory (such as /usr/pages/adp). If no directory is specified, the pages directory is assumed. The wildcards * ? and  can be included in the Map specification. You can specify multiple Map settings.
Boolean value. Set to On to restrict users from viewing the source of the Tcl script in browsers that allow HTML source to be viewed. If the HTTP client sends an Accept header containing text/x-server-parsed-html, the source of the file is returned. AOLpress sends this header if you view the HTML source (by clicking on the Show HTML icon or choosing "Show HTML" from the Tools menu) and then choose "Reload Without SSI" from the File menu.
The ClientDebug parameter lets you specify IP addresses to be enabled for debugging of ADPs. Alternatively, you can turn on client debugging temporarily from the /NS/Tcl/Admin pages.
Specify an IP address to be enabled for ADP debugging. If an IP address is specified with this parameter, error backtraces resulting from running an embedded Tcl script are inserted into the page. You can have multiple ClientDebug entries to specify multiple addresses. For example:
AOLserver allows caching of dynamic content. Because of the overhead involved in server-side processing of ADPs, it is extremely beneficial to minimize the number of times each page must be read from disk and parsed. By saving parsed ADPs in memory, caching allows dynamic content to be served more efficiently. Note that ADPs are parsed when they are cached, but they are not evaluated. Parsed ADPs are stored in the cache, identified by the name of the ADP. When an ADP is invoked, it is evaluated from the parsed version in the cache (if it exists) with the arguments passed to it.
If ADP caching is enabled, there will be a Cache Administration link on the /NS/Admin page of the server. You can follow the link to get to the Cache Administration page, which will allow you to empty the ADP cache.
By default, ADPs are not cached. To enable caching, you need to load the nscache.so module and turn on the CacheADP configuration parameter. There are several other configuration parameters you can set to customize caching for a server. All of the configuration parameters for caching are described in the following tables.
The number of seconds after which a cache entry will automatically expire and be removed from the cache. The ADP cache uses any Expires headers that are set when the ADP is served to determine when ADPs should expire from the cache. The DefaultExpires time is only used if no Expires header is set explicity by the ADP.
Boolean value. If set to On, a "stat" call is performed for each request, and the cache will detect when files have changed on disk and update them in the cache. There is a slight performance penalty in this case.
The maximum size, in kilobytes, for any single cache entry. Setting this parameter to 0 means that there is no limit to the size of a cache entry. Set this parameter to a value greater than 0 to prevent a single large file from using up too much of the cache.
The maximum number of seconds after which cache entries will be forced to expire, even if a higher value was set in the Expires header during processing. The default value, 10800, is equivalent to 3 hours.