Changes between Version 50 and Version 51 of ModParrotArchitecture

Timestamp:

05/10/09 15:21:54 (12 years ago)

Author:

jhorwitz

Comment:

--

ModParrotArchitecture

@@ -16 +16 @@
  * Context: a data structure containing information about the current connection
  * Interpreter: a Parrot interpreter ({{{Parrot_Interp}}})
+ * Context pool: a pool of contexts that implements interpreter pools for threaded MPMs
 
 == mod_parrot Module ==
@@ -39 +40 @@
 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.
 
-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}}}.
+For libraries loaded via {{{load_bytecode}}}, you can add paths to Parrot's library search path with {{{ParrotLibraryPath}}}.
 
 '''Loading Code'''
@@ -192 +193 @@
     char *name;
     modparrot_module_info *minfo;
+    const char *ctx_pool_name;
+    apr_array_header_t *ctx_pool;
     Parrot_PMC cfg;
 };
@@ -217 +220 @@
 === Module Scope ===
 
-Apache makes an obvious but significant assumption about module code.  It assumes your code knows the module to which it belongs.  So the code for mod_cgi KNOWS it's part of mod_cgi, and, as an example, its response handler can ask for the mod_cgi configuration structure appropriately.  So Apache provides no infrastructure for asking it what module code it's currently executing -- it assumes you know who you are.
+Apache makes an obvious but significant assumption about module code.  It assumes your code knows the module to which it belongs.  For example, code in mod_cgi KNOWS it's part of mod_cgi, and, as an example, its response handler can ask for the mod_cgi configuration structure appropriately.  So Apache provides no infrastructure for asking it what module code it's currently executing -- it assumes you know who you are.
 
 This is a big problem for mod_parrot, which provides SHARED hooks to support multiple HLL modules.  The same hook is called regardless of which HLL module is currently in scope, and Apache won't tell you which module it is.  This comes into play in three places:
@@ -234 +237 @@
 and retrieve the module structure:
 {{{
-    mpcfg = ap_get_module_config(our_server->module_config, &parrot_module);
-    modp = ((module **)mpcfg->module_array->elts)[module_index];
+    mpcfg = ap_get_module_config(mp_globals.base_server->module_config,
+        &parrot_module);
+    modp = ((module **)mp_globals.module_array->elts)[module_index];
 }}}