Rob Kinyon wrote:
Very cool. That, in my mind, has been the largest obviously visible stumbling block to C::A / mod_perl integration.
Also, and I know this may be more trouble than it's worth, but it might be useful to write a C::A::Plugin::Apache2 so that both AP1 and AP2 can be supported easily. I'm not sure if there's an environment variable or some other test that could be used to see if the module is being pulled into a mp1 or mp2 environment. If that were the case, then the C::A::P::Apache should probably delegate to C::A::P::Apache1 vs. C::A::P::Apache2, if possible.
Not more trouble then it's worth, but maybe more than I can do right now. :) I'll need to get a mod_perl2 setup going before I can really do any targeted development for it. And yes there is an environment var that most of the modules look at when trying to do both. I'll probably just keep it in the same module and alter it's behavior accordingly.
Just some rambling thoughts. :-)
Rob
On Thu, 21 Oct 2004 14:00:05 -0400, Michael <[EMAIL PROTECTED]> wrote:
Rob Kinyon wrote:
Would you be able to add a handle() method here that would dispatch to the various runmodes, so that way I could just use my C::A child as a mod_perl handler without thinking about it?
yea I would :)
On Thu, 21 Oct 2004 13:29:23 -0400, Drew Taylor <[EMAIL PROTECTED]> wrote:
On Thu, 21 Oct 2004 12:44:12 -0400, Michael <[EMAIL PROTECTED]> wrote:
Here is the initial documentation from an idea I'm playing with and wanted to get some feedback on. I've attached the code to this message as well...
HTTP Headers * Cookies HTTP headers (and hence HTTP cookies) are now not created with "header_add()" or "header_props()". Instead use Apache::Cookie for cookies and anything you want for additional header manipulation.
* Redirects This also means that the "$self->header_type('redirect')" doesn't currently do anything. Instead you should use "$self->query->internal_redirect($some_url)" for external redirects and use something like
$self->query->header_out(Location => $some_url); $self->query->status(REDIRECT);
First, I really like the idea. A client of mine is a recent convert to CGI::App but would really like to use Apache::Request. This makes it very easy to do.
A couple comments: Is there any reason you can't provide overridden header_*() method which Do The Right Thing under the hood? This would make it trivial to switch between use of CGI & Apache::Request. I know that it's probably not practical to have 100% API compatibility, but covering the header method would go a long way.
Drew -- ---------------------------------------------------------------- Drew Taylor * Web development & consulting Email: [EMAIL PROTECTED] * Site implementation & hosting Web : www.drewtaylor.com * perl/mod_perl/DBI/mysql/postgres ----------------------------------------------------------------
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Michael Peters Developer Plus Three, LP
-- Michael Peters Developer Plus Three, LP
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
