On Fri, Oct 22, 2004 at 10:16:21AM -0400, Michael wrote:
Maybe I need to think about this more and hear other's ideas before I implement it.
Initially I had similar concerns that supporting both environments could lead to all sorts of headaches. However, this is a plugin, not the default behavior. I think some stern warnings in the POD would be sufficient to advise informed users of what to avoid and to scare off newbies who should just stick with using CGI.pm.
Otherwise, I really like the idea of having a plugin that gives me better performance under mod_perl but still works under mod_cgi.
Well then, should I add this by trying to duplicate the C::A code if there is no $ENV{MOD_PERL} or should I just call $self->SUPER::cgiapp_get_query or $self->SUPER::_send_headers? Since the plugin exports these methods to the application class then it should work just fine and then C::A could actually change without me having to worry.
Also, should we look at making _send_headers into send_headers in case other modules want to subclass this behaviour as well?
-- 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]
