Changes between Version 26 and Version 27 of ModParrotArchitecture

Show
Ignore:
Timestamp:
11/30/08 19:50:20 (6 years ago)
Author:
jhorwitz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ModParrotArchitecture

    v26 v27  
    106106=== Parrot Objects === 
    107107 
     108== Parrot Interface == 
     109 
     110=== NCI Functions === 
     111 
     112=== Parrot Objects === 
     113 
    108114== HLL Modules == 
    109115 
     116In addition to the global mod_parrot Apache module, each HLL layer must register its own Apache module.  This is a first-class module, and Apache cannot tell it apart from any other module.  Having separate Apache modules for each HLL pushes things like configuration management, hook dispatch, and error semantics onto Apache, which is designed to do just those things.  This keeps mod_parrot small, generic and flexible. 
     117 
    110118=== Module Registration === 
     119 
     120The following information is required to register a module: 
     121 
     122 * A unique module name.  The convention is modparrot_HLLNAME_module (replace HLLNAME with the name of your HLL) 
     123 * The namespace where your module code lives.  HLL module code is required to live in a nested namespace under the {{{ModParrot;HLL}}} namespace.  If your code lives in {{{ModParrot;HLL;perl6}}}, specify {{{perl6}}} as your namespace. 
     124 * An array of hashes describing the HLL's custom Apache directives (this is optional). 
     125 * An array of hook enums that your module will handle. 
     126 
     127This information is used to register the module via Apache;Module;add_module().  See the [wiki:ModParrotHLLDocs HLL module developer guide] for details on its usage. 
     128 
     129=== Module Configuration === 
    111130 
    112131=== Metahandlers ===