Changes between Version 21 and Version 22 of ModParrotArchitecture
- Timestamp:
- 11/30/08 19:28:11 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ModParrotArchitecture
v21 v22 33 33 mod_parrot itself requires very little configuration, and most of it should be done from the HLL layer. Most tunables have corresponding Apache directives that you can use in httpd.conf. 34 34 35 '''Initialization''' 36 37 mod_parrot bootstraps itself by loading {{{mod_parrot.pbc}}}. If not otherwise specified, Parrot will look for it in its library search path (see below). You can explicitly specify the path to {{{mod_parrot.pbc}}} with the {{{ParrotInit}}} directive. 38 35 39 '''Paths''' 40 41 If you are running handlers written in PIR and are including files from the Parrot runtime directory via {{{.include}}}, you will need to set the {{{PARROT_RUNTIME}}} environment variable. This is not required if you have compiled your handlers to PBC. 42 43 For libraries loaded via {{{load_bytecode}}}, you can add paths to Parrot's library search path with {{{ParrotIncludePath}}}. The name of this directive is misleading and will eventually be renamed to {{{ParrotLibraryPath}}}. 36 44 37 45 '''Options''' … … 41 49 ||MP_OPT_PARENT||Parent||Off||Dedicates a separate context pool for a virtual host|| 42 50 ||MP_OPT_TRACEINIT||!TraceInit ||Off||Trace mod_parrot initialization code (can be verbose)|| 43 44 51 45 52 === Contexts ===