On Sun, 2005-02-13 at 16:28 +1100, Bojan Smojver wrote: > I'm not sure why constructing a request would be so unusual. Application > servers running inside Apache may need to do this stuff all the time.
Just a little clarification here. The text here: http://httpd.apache.org/docs-2.0/developer/request.html#processing Does mention "generated requests" in relation to modules: "All requests pass through ap_process_request_internal() in request.c, including subrequests and redirects. If a module doesn't pass generated requests through this code, the author is cautioned that the module may be broken by future changes to request processing." Therefore, I was under the impression that this is a normal thing for modules to do (i.e. generate requests). Unfortunately, not all functions required to do so fall under the "public" API. Maybe I should approach my problem differently. Maybe I should be writing a patch for yet non-existent function ap_generate_request(), along the lines of that mod_perl function. Then this new function becomes "public" and CORE_PRIVATE remains truly private... And, all module writers can rely on this function for creation of "vanilla" requests. In any event, I think separating everything under CORE_PRIVATE into separate, non-installable headers is the right thing to do. Would patches along those lines be welcome? -- Bojan
