CSP Control Console
| You can open the CSP Control Console by clicking on the Windows "Start" button and choosing Programs | C++ Server Pages | CSP Control Console. The list below describes the various features and fields that appear in the CSP Control Console. Engine dir.: The main directory of the CSP Engine that contains critical files and directories. Modules dir.: The working directory that contains the binaries (*.dll) of the compiled scripts. Include path: The path that the compiler will search for included files, such as C/C++ header files (*.h, *.hpp, *.hxx). This path may contain many directories seperated by the semicolon (;) character. Lib path: The path that the linker will search for import libraries (*.lib, *.a). This path may contain many directories seperated by the semicolon (;) character. Execution Path: The path that the engine will search for executable or any other type of files. This path may contain many directories seperated by the semicolon (;) character. Custom or third party DLLs that are used by the CSP scripts, should be copied in one of this path's directories. Session Manager: The full path to the SessionManager .dll file. Application Manager: The full path to the ApplicationManager .dll file. Compiler command line: The command line used for the compiling scripts. The tags %opt, %out, %src, are replaced by the engine defined compiler options, output filenames, and source filenames respectively. Linker command line: The command line used for linking the binaries of the compiled scripts. The tags %opt, %out, %src, are replaced by the engine defined linker options, output filenames, and source filenames respectively. Module timeout: The default module timeout. The module time out is the time since the last hit, after which a CSP script will be unloaded from the memory. If you want to override the default module timeout for a certain script, you can use the "CSP_MODULE_TIMEOUT" definition. For more information, please see the CSP Definitions. Source code changes: If this option is checked, everytime a script is requested, the engine checks whether the script has been modified or not. If modified, the script is recompiled, before it is executed. If this option is unchecked, the engine never checks for changes in the scripts, and it directly executes them. Leaving this option unchecked, results to less processing overhead per script request.
Online help home | Back
www.micronovae.com Copyright © 2002 - 2004 Micronovae