Changes between Version 8 and Version 9 of ModParrotArchitecture
- Timestamp:
- 11/29/08 15:46:36 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ModParrotArchitecture
v8 v9 5 5 == Overview == 6 6 7 This page describes the various subsystems of mod_parrot, and how they all work together. It is meant to reflect the current state of mod_parrot and should not be used for future design notes. As such, it will be kept up to date with mod_parrot trunk.7 This page describes the various subsystems of mod_parrot, and how they all work together. It will track mod_parrot trunk, so it may not accurately describe the latest release. 8 8 9 9 == Terminology == … … 27 27 The mod_parrot Apache module is the product of compilation, and is usually named {{{mod_parrot.so}}} on Unix systems. It has a dependency on libparrot.so. 28 28 29 The module alone provides no HLL layers, and thus no real functionality by itself.30 31 29 After installation, the module should be loaded as follows in the Apache configuration: 32 30 33 31 {{{LoadModule parrot_module modules/mod_parrot.so}}} 32 33 The module alone provides no HLL layers, and thus no real functionality by itself. 34 34 35 35 === Configuration === … … 61 61 === Context Pools === 62 62 63 Contexts are allocated from context pools, which contain a finite number of contexts created at startup. Contexts contain pointers to Parrot interpreters so this also provides mod_parrot with a pool of interpreters.63 Contexts are allocated from context pools, which are populated at startup and tuned dynamically at runtime. Contexts contain pointers to Parrot interpreters so this also provides mod_parrot with a pool of interpreters. 64 64 65 65 ==== Interpreter Lifecycle ====
