Table of Contents
- Introduction
- Installation
- Handling Challenger
- Virtual Servers
- Configuration Examples
- Modules
- Filesystems
- RXML Tags
- Graphics
- Proxy
- Databases
- Miscellaneous Modules
- Security Considerations
- Scripting

  | · Introduction · Pike Modules · Pike Scripts · Pike Tag · CGI · SSI · FastCGI · Servlets

- Frontpage
- Upgrading
- Third Party Extensions
- Portability
- Reporting Bugs
- Appendix

Pike Scripts
Pike scripts are an easy and quick way of doing scripting in Challenger. Since Pike is also the language that Challenger uses internally, Pike scripts are efficient, and with them practically anything that can be done in Challenger can be done.

Support for Pike scripts in Roxen Challenger is provided by two different modules, the general Pike script support module, and the Restricted Pike script support module. The difference is mainly that while the former gives the scripts access to the whole server, the latter runs each user's scripts in a separate server process running with that user's access privileges, greatly reducing the potential security problems that might result from faulty scripts.

As with Pike modules, error messages are reported complete with a Pike backtrace. This makes development fast since it is simple to pinpoint the problem.

Pike scripts are usually persistent. That means they will be compiled only once, and invoked repeatedly. This makes them fast and efficient.

Pike script support

`Extensions`
  The extensions of Pike scripts.

`Fork execution`
  Whether to invoke Pike scripts by forking or handle them internally. Forking is slower and uses more resources but is also more secure since the forked script will run as the user who owns the script and cannot take control over the server.

  Fork execution does not work with threading.