> I'm still not sure what's the best option: > 1) add a new option: PerlOptions +NonParseHeaders > 2) /nph-/ in registrycooker > in either case call $r->assbackwards(1); > > The reason I don't like (1) is that it adds a (tiny) overhead which is > totally unnecessary for 99.9999% of handlers,
you mean each new option adds more request-time overhead? > which can call > $r->assbackwards(1) if they need to. It's only registry scripts that > need to run under mod_cgi that need to emulate mod_cgi, therefore (2) > seems to be the simplest solution. or we can even add > ModPerl::RegistryNPH which will just call $r->assbackwards(1); for > those special cases. I think I'd prefer the new subclass over adding nph support to Registry.pm. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
