Configuring ADP Processing
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.
Required Configuration Parameters
- Use the Map configuration parameter (see page 7) to determine which files are to be processed. For example, you can specify that all files with the .adp extension are to be processed by the server. Or, you can specify that all files that reside in a certain directory (for example, /usr/pages/adp) will be processed.
- If you want to register your own ADP tags, you must set the Fancy parameter to On. It also allows you to use the <server> ... </server> ADP syntax and determine whether ADP tags can be registered after startup.
List of Configuration Parameters
The following table describes all the parameters that can be set within the ADP section of the configuration file:
Boolean value. If set to on, ADP caching is enabled.
The procedure to run when debugging begins.
Boolean value. If set to on, the "Expires: now" header is set on all outgoing ADPs.
Boolean value. If set to on, extraneous spaces within an HTML page are removed.
Boolean value. If set to on, appending "?debug" to a URL will enable TclPro debugging.
Boolean value. If set to on, "fancy" ADPs are enabled, meaning that:
the TagLocks parameter is enabled
the <server>...</server> syntax is enabled
the ns_register_adptag and ns_adp_registertag commands are enabled
registered ADP tags are enabled
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.
The following example specifies that all files in the pages directory with the extensions .adp or .asp will be parsed, and all files in the /usr/pages/myadps directory will be parsed.
The file to be run on every connection instead of the requested ADP. It can be used to perform routine initialization. It would then usually include the requested ADP by calling:
ns_adp_include [ns_adp_argv 0]
Boolean value. If set to on, ADP tags may be registered after server startup. Pages will be served less quickly when this is turned on.
If set to off, ADP tags can only be registered before the first ADP is served.