Context Navigation

Changes between Version 26 and Version 27 of ModParrotArchitecture

v26	v27
106	106	=== Parrot Objects ===
107	107
	108	== Parrot Interface ==
	109
	110	=== NCI Functions ===
	111
	112	=== Parrot Objects ===
	113
108	114	== HLL Modules ==
109	115
	116	In 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
110	118	=== Module Registration ===
	119
	120	The 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
	127	This 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 ===
111	130
112	131	=== Metahandlers ===