PerlEx includes a number of examples to help you get started. To run the examples, click the Examples tab at the top of the Table of Contents pane.
Note: the examples assume that PerlEx is installed on this
machine, and that the address
http://localhost/PerlEx/scriptname
is valid.
If you have difficulties running the following examples, see the FAQ entry I can't get any of the samples to work, what should I do?.
By default, during the PerlEx installation routine, PerlEx associates the
file extensions ".plex" and ".aspl" with PerlEx. Additionally, PerlEx
creates a virtual directory mapping with the appropriate permissions to
the directory <PerlPath>/eg/PerlEx
(where
<PerlPath> is the location of your ActivePerl installation).
First, read How PerlEx Works. This describes the PerlEx precompiler, threading behavior and interpreter classes.
Second, ensure that your scripts adhere to PerlEx's extension format. By default, scripts with the extension ".plex" (standard scripts) and ".aspl" (embedded scripts) are handled by PerlEx. To add additional extensions, refer to the Script Mappings section of the Web Server Configuration topic.
Third, optimize your scripts to work with PerlEx.
If necessary, create Interpreter Classes to segregate scripts as you optimize them for PerlEx. Using Interpreter Classes, you can configure the Interpreter value for one or more scripts. See the PerlEx FAQ.